Skip to content

docs: release process must match what the workflow actually matches - #54

Merged
danielgines merged 1 commit into
mainfrom
docs/release-process-matches-workflow
Aug 23, 2026
Merged

docs: release process must match what the workflow actually matches#54
danielgines merged 1 commit into
mainfrom
docs/release-process-matches-workflow

Conversation

@danielgines

Copy link
Copy Markdown
Member

O CONTRIBUTING mandava commitar release: vX.Y.Z e taggear à mão. O .github/workflows/release.yaml casa chore(release): vX.Y.Z e faz a tag sozinho.

Seguir o documento produz tag sem GitHub Release, e nenhum erro em lugar nenhum — o workflow roda, não casa nada e sai verde. Foi o que aconteceu no v0.44.0 (Release publicada manualmente depois).

Corrige o procedimento e documenta os dois modos de falha silenciosa: subject diferente, e squash merge (que reescreve para chore(release): vX.Y.Z (#NNN) e não casa a regex ancorada).

CONTRIBUTING said to commit "release: vX.Y.Z" and tag by hand. The workflow
matches "chore(release): vX.Y.Z" and does the tagging itself, so following the
document produced a tag with no GitHub Release and no error anywhere — which is
exactly what happened on v0.44.0.
@danielgines
danielgines merged commit 7c1906b into main Aug 23, 2026
5 checks passed
@danielgines
danielgines deleted the docs/release-process-matches-workflow branch August 23, 2026 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant