ci: trigger a satis rebuild when a release is cut - #32
Merged
Merged
Conversation
Tagging v0.6.3 did not make the release installable: the satis index at generoi.github.io/packagist only re-reads tags on its 3h cron, so `composer update generoi/gds-mcp` reported "Nothing to modify in lock file" and kept resolving the previous commit. The mirror had to be rebuilt by hand. 63 of the 72 vcs packages in satis already call the shared rebuild hook. This repo was one of the 9 that did not — it only ever had test.yml. Fires on both a published Release and a `v*` tag push, since both are used to cut versions across these repos. Needs PACKAGIST_UPDATE_PAT granted to this repo to take effect; without the grant it warns and falls back to the cron, which is the pre-existing behaviour. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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.
Problem
Tagging v0.6.3 did not make the release installable. The satis index at
generoi.github.io/packagistonly re-reads tags on its 3h cron, so consumers got:Composer exits 0 and keeps the previous commit — the failure is completely silent. The mirror had to be rebuilt by hand before btb-transformers could pull the fix.
Context
63 of the 72
type: vcspackages in satis already call the shared rebuild hook. This repo was one of 9 that did not; it only ever hadtest.yml. The same gap affectsgds-block-animations,gds-content-translationandgravityforms-elisadesk(PRs opened separately).Change
Adds
.github/workflows/release.ymlcalling the shared reusable workflow, matching whatgds-assistant,b2b-rolesandgravityforms-altchaalready do.Triggers on a published Release and a bare
v*tag push — both are used to cut versions across these repos (gds-block-animationshas av0.2.0tag with no corresponding Release). Firing twice is harmless: the rebuild is idempotent andsatis.ymlserialises runs viaconcurrency.Requires a secret grant to actually take effect
PACKAGIST_UPDATE_PATis an org secret scoped to selected repositories. Untilgeneroi/gds-mcpis added to the allow-list,update.ymlwarns and exits green by design, and releases keep landing via the 3h cron — i.e. no worse than today, just not yet better.Grant it here: https://github.com/organizations/generoi/settings/secrets/actions/PACKAGIST_UPDATE_PAT
🤖 Generated with Claude Code