Skip to content

chore: force release 5.1.0 instead of 6.0.0#410

Merged
davidf-null merged 1 commit into
mainfrom
chore/release-as-5.1.0
Jun 25, 2026
Merged

chore: force release 5.1.0 instead of 6.0.0#410
davidf-null merged 1 commit into
mainfrom
chore/release-as-5.1.0

Conversation

@davidf-null

Copy link
Copy Markdown
Collaborator

Qué hace

Fuerza a release-please a publicar la próxima versión como 5.1.0 (minor) en lugar de 6.0.0 (major), mediante el footer `Release-As: 5.1.0` en un commit vacío.

Por qué

El PR de release #407 calculó 6.0.0 porque el commit de #397 (`feat(iam/agent): split agent role into agent + permissions roles`) incluye un footer `BREAKING CHANGE:`, que fuerza un major bump (v5.0.0 → 6.0.0). Se decidió tratarlo como un cambio minor.

⚠️ Importante al mergear

Para que release-please vea el footer `Release-As: 5.1.0`, mergear con "Create a merge commit" (NO squash), así el commit con el footer queda en el historial de `main`. Tras el merge, release-please re-corre y actualiza el PR #407 a `5.1.0`.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Release-As: 5.1.0
@davidf-null davidf-null merged commit fc5ef69 into main Jun 25, 2026
44 checks passed
@davidf-null davidf-null deleted the chore/release-as-5.1.0 branch June 25, 2026 18:42
This was referenced Jun 25, 2026
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