chore: refine Docker image tagging strategy for releases#10
Merged
Conversation
resendegu
approved these changes
Oct 1, 2024
Tutuviz
approved these changes
Oct 1, 2024
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
3 participants
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.
A mudança principal é garantir que as tags
latest,majoreminorsejam atualizadas apenas para releases completas, não para pré-releases.Impacto
majorouminor, proporcionando um ambiente mais estável e seguro.Exemplo
Se lançar uma tag com pré-release habilitado como
v1.6.9-beta, o resultado será o seguinte:1.6.9-beta(gerada pela regra type=semver,pattern={{version}})sha-abcdef1(supondo que 'abcdef1' seja os primeiros 7 caracteres do SHA do commit)Se for uma
releasefinal será atualizado todas as regras dosemver.Evidências
Link: https://github.com/cubos/cli/actions/runs/11126593346/job/30916874908