Conversation
The image workflow has been publishing to ghcr.io/bb-ricardo/netbox-sync next to Docker Hub for every development build and tag. Make the GHCR address the documented one in the README and in the Kubernetes CronJob example, and say that v1.9.0 is the last release pushed to Docker Hub so current users get one release cycle to switch. The workflow keeps pushing to both registries for this release; the Docker Hub steps go away after it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The workflow has been pushing to
ghcr.io/bb-ricardo/netbox-syncnext to Docker Hub for every development build and tag (multi-arch, and the package is public: an anonymousdocker pull ghcr.io/bb-ricardo/netbox-sync:developmentworks). This makes the GHCR address the documented one in the README and in the Kubernetes CronJob example, and states that v1.9.0 is the last release pushed to Docker Hub, as agreed in #474, so current users get one release cycle to switch. No workflow change: both registries still receive v1.9.0; the Docker Hub steps come out after the release.