Repository navigation
Hotfix 0.18.1: sync the open release with main through a PR - #142
Closed
djessyczaplicki-genomcore wants to merge 3 commits into
Closed
djessyczaplicki-genomcore wants to merge 3 commits into
djessyczaplicki-genomcore wants to merge 3 commits into
Conversation
Open a PR from main into the open release branch on every push to main, so hotfixes and docs/ tickets reach the release that ships next. The Release Guard ruleset blocks direct pushes to release/**, so the sync goes through a PR.
…en when there is one The PR head is now sync/<release>, pointed at main, so its conflicts can be resolved in the PR without touching main, and every push to main moves it forward while it has no commits of its own. With the SYNC_RELEASE_APP_ID variable and SYNC_RELEASE_APP_KEY secret, the PR is opened with that App's token, so its required checks run.
Contributor
Author
|
Cerrada: todo entra con la release, en #145. |
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
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.
Hotfix 0.18.0 → 0.18.1: añade el workflow
Sync release with main(.github/workflows/sync-release.yml). Sustituye a #141, que iba contrarelease/2026-11-17.Qué hace
En cada push a
main(y a mano con Run workflow):release/AAAA-MM-DDmás reciente.maino si ya contiene todo lo demain.sync/<release> → releaseabierta, avanzasync/<release>hastamain, salvo que tenga commits propios (conflictos ya resueltos): entonces no la toca.sync/<release>amainy abre la PRsync/<release> → release/AAAA-MM-DD.La cabeza de la PR es
sync/<release>y nomainpara que los conflictos se puedan resolver en la propia PR (editor de GitHub o push async/…) sin tocarmain.Si el repo tiene la variable
SYNC_RELEASE_APP_IDy el secretSYNC_RELEASE_APP_KEY, la PR se abre con el token de esa GitHub App y le corren los checks obligatorios. Sin ellos usaGITHUB_TOKEN, como antes.El ruleset Release Guard no deja hacer push directo a
release/**, así que la sincronización va por PR, con su approval y sus checks.Versión
plugin.jsonymarketplace.jsona 0.18.1, sección## 0.18.1enCHANGELOG.md(sin nada que hacer en los proyectos) yplugin/manifests/0.18.1.json, generado desde el commit del bump. Es idéntico al de 0.18.0 porque el runtime no cambia.template-runtime-version.sh --checkpasa en local.Al mergear,
Daily releasecrea el tagv0.18.1y la GitHub Release.A tener en cuenta
CHANGELOG.md: la release de hoy ya lleva 0.19.0. Al resolverlo, hay que quedarse con la versión de la release.GITHUB_TOKENno lanzan otros workflows: hasta que esté la GitHub App, si a la PR de sync no le salen los checks, hay que cerrarla y reabrirla. La App necesita permisos de Contents, Pull requests y Workflows (lectura y escritura) en el repo.REQUIRE_APPROVAL_ON_HEAD). Mejor mergear las syncs antes de aprobar.retargetde la daily intente reapuntar la PR de sync (daba 422 y cortaba el bucle) y cierra las que se quedan colgando. Tiene que entrar enrelease/2026-11-17antes de que se publique.release/2026-11-17con los 2 tickets dedocs/que están enmainy no en la release.🤖 Generated with Claude Code