Repository navigation
fix(portainer): follow the major image tag in the stack - #165
Merged
Merged
Conversation
The catalog guide recommends a major tag: users get fixes on Pull and redeploy without a breaking upgrade, and the compose no longer needs a bump on every release.
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
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 Portainer catalog guide recommends a major image tag over an exact release: a stack gets fixes on Pull and redeploy without a surprise breaking upgrade, and the compose no longer has to be bumped on every release, which also removes the window where it names an image not yet published. Moving to a new major version stays a deliberate change of this line.