build(docker): always publish full and minor version tags for dev images #306
Conversation
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
|
I expect the backports to fail but at least they will be a starting point. |
1c07739 to
0c340e1
Compare
0c340e1 to
52c14b7
Compare
52c14b7 to
d51f752
Compare
|
Backport assistant died. . Going in manually. |
This was referenced Oct 18, 2023
This was referenced Oct 18, 2023
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.
Always publishing full and minor-only tag versions. This accomplishes two goals:
.x, always publish a minor-only tag so that tests use the latest version (e.g.1.4-dev).0, always publish the full version so we can fix this for testing purposes (e.g.1.3.0)