Skip to content

Docker Publishing and other workflow updates - #681

Open
Zeitsperre wants to merge 15 commits into
masterfrom
docker-deployment
Open

Docker Publishing and other workflow updates#681
Zeitsperre wants to merge 15 commits into
masterfrom
docker-deployment

Conversation

@Zeitsperre

@Zeitsperre Zeitsperre commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Closes #662

Changes

  • Replaced bump2version with bump-my-version.
  • Updated ReadTheDocs base image to ubuntu-26.04.
  • Added metadata fields to Dockerfiles using modern conventions.
  • Added cooldowns to Dependabot.
  • Set all GitHub Actions to use commit hashes of versions.
  • Added a Docker Hub publishing workflow for both Magpie and Twitcher w/MagpieAdapter

@github-actions github-actions Bot added the ci Something related to code tests, deployment and packaging label Aug 25, 2026
@github-actions github-actions Bot added the tests Test execution or additional use cases label Aug 25, 2026
@Zeitsperre Zeitsperre self-assigned this Aug 25, 2026
@Zeitsperre
Zeitsperre marked this pull request as ready for review August 25, 2026 21:02

@fmigneault fmigneault left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The hooks/ should be removed since not needed anymore.

Comment thread .github/workflows/docker-publish.yml
Signed-off-by: Trevor James Smith <10819524+Zeitsperre@users.noreply.github.com>
@Zeitsperre

Copy link
Copy Markdown
Contributor Author

The hooks/ should be removed since not needed anymore.

Are you sure you want these removed? If they still work, you could still have the option to manually upload built images.

@fmigneault

Copy link
Copy Markdown
Member

Are you sure you want these removed? If they still work, you could still have the option to manually upload built images.

Hooks are part of the automated build (https://docs.docker.com/docker-hub/repos/manage/builds/advanced/), I expect them to not be functional anymore once it is fully retired.

I think its ok anyway. There are make targets for build/push each of them if needed manually, and the CI should take care of them for releases. I would actually rather make sure DockerHub doesn't do duplicate auto-builds that the CI should do in the meantime will the features still exists.

@Zeitsperre
Zeitsperre requested a review from fmigneault August 27, 2026 15:47

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still needed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Something related to code tests, deployment and packaging tests Test execution or additional use cases

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Docker Publish

2 participants