Philip Durbin 🚀 (Jul 01 2026 at 20:15): Philip Durbin 🚀 (Jul 01 2026 at 20:15):I released 6.11 and it kicked off https://github.com/IQSS/dataverse/actions/runs/28542324468/job/84625616643 but I'm confused.
Philip Durbin 🚀 (Jul 01 2026 at 20:15):The following tags were updated:
6.9-noble-r14
Last pushed 3 minutes by dataversebot
--
6.9-noble
Last pushed 3 minutes by dataversebot
--
6.10-noble-r7
Last pushed 5 minutes by dataversebot
--
6.10-noble
Last pushed 5 minutes by dataversebot
--
6.10.1-noble-r6
Last pushed 7 minutes by dataversebot
--
6.10.1-noble
Last pushed 7 minutes by dataversebot
Philip Durbin 🚀 (Jul 01 2026 at 20:15):But the "latest" tag wasn't updated? It shows this:
latest
--
Last pushed 25 days by dataversebot
Philip Durbin 🚀 (Jul 01 2026 at 20:18):And the 6.11 tag was updated two months ago?
6.11-noble
--
Last pushed about 2 months by dataversebot
Philip Durbin 🚀 (Jul 01 2026 at 20:19):Shouldn't the "latest" and "6.11-noble" tags have been updated when I released 6.11?
Philip Durbin 🚀 (Jul 01 2026 at 20:19):Here's a loooong screenshot, if it helps:
Philip Durbin 🚀 (Jul 01 2026 at 20:22):Should I manually run the job again to see if that fixes it? https://github.com/IQSS/dataverse/actions/workflows/container_maintenance.yml
Philip Durbin 🚀 (Jul 01 2026 at 20:23):The context for this is that I'm updating the steps in the "making releases" doc to explain how to test the "latest" image after a release.
Philip Durbin 🚀 (Jul 01 2026 at 20:23):This is what I have so far:
Test Docker Images
Publishing the release should have trigged the "Container Images Scheduled Maintenance" GitHub Action. Allow it to finish and then go to https://hub.docker.com/u/gdcc and navigate to "gdcc/dataverse".
Click on "tags", make sure the "latest" tag has been updated, and then spin it up locally, after deleting old images:
docker rmi gdcc/dataverse:latest
docker rmi gdcc/configbaker:latest
cd docker/compose/demo
rm -rf data
docker compose up
Wait for the bootstrapping process to complete. Then, make sure the version returned by http://localhost:8080/api/info/version matches the version you are releasing.
Philip Durbin 🚀 (Jul 01 2026 at 20:24):But the version won't be updated until the images are pushed, obviously.
Philip Durbin 🚀 (Jul 01 2026 at 20:45):Philip Durbin 🚀 said:
Should I manually run the job again to see if that fixes it? https://github.com/IQSS/dataverse/actions/workflows/container_maintenance.yml
I went ahead and kicked off a run, on the develop branch: https://github.com/IQSS/dataverse/actions/runs/28546582863
Philip Durbin 🚀 (Jul 02 2026 at 00:07):Oh, good, that worked!
Philip Durbin 🚀 (Jul 02 2026 at 00:07):The "latest" tag was updated after I manually ran the job again:
Philip Durbin 🚀 (Jul 02 2026 at 00:08):I documented this workaround for the next time we do a release: https://github.com/IQSS/dataverse/pull/12507/changes/18d9e3417fd7ac4ccbd55cfb662d8f108e02460b
Philip Durbin 🚀 (Jul 02 2026 at 19:50):@Oliver Bertuch added to #12507. If you don't mind approving it, I'll merge it!
Philip Durbin 🚀 (Jul 07 2026 at 11:21):@Oliver Bertuch at standup yesterday I asked the team to look at #12507 and approve it if they're ok with it, which they were (@Steven Winship took a look, thanks). I can go ahead and merge it. Or you can look first. What do you think? It's just docs explaining the workaround of rerunning the job if necessary (and some other release-related docs). This is the part to focus on: https://dataverse-guide--12507.org.readthedocs.build/en/12507/developers/making-releases.html#test-docker-images
Philip Durbin 🚀 (Jul 09 2026 at 14:21):@Oliver Bertuch I went ahead and merged #12507. I got tired of looking at it on the board. :smile: We can follow up with another PR if I got anything wrong! :sweat_smile:
Last updated: Aug 18 2026 at 08:27 UTC