ci(repo-state): adopt family-os v0.19.0 (workflow_run after release-sync) (family-os#165) - #64
Merged
Merged
Conversation
…ync) (family-os#165) Adds on: workflow_run for the release-sync workflow so the stamp refreshes after a GITHUB_TOKEN-created Release, and bumps uses:/generator_ref together to v0.19.0. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
shojikumaru
added
the
risk-reviewed
github-actions
Bot
added
the
needs-risk-review
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
2 participants
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.
Why
Follow-up to caty-ai/family-os#165 (fix merged as family-os PR #170, released as v0.19.0). With v0.18.0 the stamp refreshes on every
updaterun, but a Release created by release-sync withGITHUB_TOKENfires noreleaseevent, so a repo that releases and then goes quiet keeps the previouslatest_taguntil its next unrelated push. v0.19.0 adds aworkflow_runpath: when this repo'srelease-syncworkflow completes successfully, the reusableupdatejob checks out the default branch and refreshes the stamp.What (mechanical diff)
.github/workflows/repo-state.yml:on:gainsworkflow_run: workflows: [release-sync], types: [completed](this repo's carrier is namedrelease-sync)uses: …/repo-state.yml@v0.19.0+generator_ref: v0.19.0(refs move together per the caller contract)Nothing else changes. Generator unchanged since v0.12.1.
Behaviour after merge: one extra
updaterun per release (after release-sync completes; failed/cancelled carrier runs do not trigger it), which regenerates and pushes a stamp commit only iflatest_tagchanged. Details: family-osdocs/repo-state/spec.md§4.Review
Batch of 13 caller adoptions, one heterogeneous delta seat over the whole batch diff (the family-os#127 owner-approved lighter scheme for mechanical copies, as used for the v0.18.0 bump on #163). Seat record on caty-ai/family-os#165.
完了記録 (Completion record)
candidate SHA: c72b60b
implementer: Alpha (Claude Fable 5.1) — mechanical yml edit (3-line trigger + 2 pin lines)
reviewer: BATCH_SEAT
identity check: 別モデル
CI: see PR checks at merge time (recorded on family-os#165 per repo)
release: N/A ③ (CI wiring only — the caller trigger and pin; no behaviour, API or artifact of this repository changes)
previous release: unchanged by this PR (no ship-equivalent change here); ledger continues on this repo's next ship-equivalent lane
Done when → 結果
workflow_runonrelease-syncand pins@v0.19.0/generator_ref: v0.19.0latest_tagrefreshes without a further pushworkflow_runrun + stamp commitTracked in caty-ai/family-os#165.
🤖 Generated with Claude Code