docs: document the release flow under the protected main branch - #15
Merged
Merged
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
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.
mainpassou a exigir pull request e checks verdes, sem bypass. O commit derelease, que até a v0.19.1 ia direto pra
main, agora também precisa de PR — eisso não estava escrito em lugar nenhum.
Acrescenta uma seção Cortando uma release ao CONTRIBUTING.md com o ciclo
completo: os três arquivos que o commit de release toca (CHANGELOG, VERSION e o
docs/commands.jsonregenerado), o PR, e só depois a tag apontando para ocommit já em
main— ordem que o própriorelease.ymlcobra.Registra também que o ruleset cobre só
refs/heads/main, então o push da tagcontinua direto, e que a fórmula do tap é reescrita pelo workflow.
Documentação apenas; nenhuma mudança de código.