fix: repõe no changelog o conserto do OAuth dos builds de release - #465
Merged
Conversation
O release-please lê o prefixo Conventional Commits do assunto do squash; com o default antigo (mensagem do commit em PR de commit único), o prefixo se perdia e lançamentos como o conserto do OAuth dos builds de release saíam do changelog.
johnlaff
added a commit
that referenced
this pull request
Aug 15, 2026
🤖 I have created a release *beep* *boop* --- ## [0.3.1](v0.3.0...v0.3.1) (2026-08-15) ### Bug Fixes * repõe no changelog o conserto do OAuth dos builds de release ([#465](#465)) ([361dbc1](361dbc1)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: johnlaff <46091881+johnlaff@users.noreply.github.com>
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.
O PR #464 fez os builds de release do desktop embutirem o Google client id, mas seu squash entrou no main sem o prefixo Conventional Commits — num PR de commit único, o GitHub usava a mensagem do commit (sem prefixo, pela convenção do repo) como assunto do squash, e o release-please descartou o conserto como "não user-facing": a 0.3.1 nunca nasceu.
Este PR conserta a causa e o sintoma: a configuração do repositório passou a usar o título do PR como assunto do squash e o corpo do PR como mensagem (o que também torna o Closes #N deliberado, nunca herdado de commit antigo), o AGENTS.md documenta a regra, e o próprio squash deste PR — com prefixo fix: — devolve ao release-please o lançamento pendente que carrega o conserto do OAuth para os usuários da versão instalada.
Como verificar: após o merge, o release-please deve abrir o PR da release 0.3.1 contendo este conserto no changelog.