chore(repo-state): pin caller to family-os v0.18.0 (family-os#163) - #63
Merged
Merged
Conversation
Reusable workflow v0.18.0 refreshes latest_tag / latest_release_url on every update run. uses: and generator_ref move together per the caller contract. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
github-actions
Bot
added
the
needs-risk-review
shojikumaru
added
the
risk-reviewed
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#163 (fix merged as family-os PR #166, released as v0.18.0). Until this bump, this repo's
status.json.latest_tag/latest_release_urlnever refreshed after a release-sync Release, because Releases created withGITHUB_TOKENdo not fire thereleasetrigger and the pinned reusable workflow only refreshed on that event. v0.18.0 refreshes on everyupdaterun (push included).What (mechanical diff)
.github/workflows/repo-state.yml:uses: …/repo-state.yml@v0.18.0+generator_ref: v0.18.0(refs move together per the caller contract). Nothing else changes. The generator itself is unchanged since the current pin; only the reusable workflow's refresh gate moved.Behaviour after merge: each
updaterun makes onegh api repos/{repo}/releases/latestcall withGITHUB_TOKEN(at most two with the rebase retry); a non-404 API failure fails that stamp run (fail-closed; readers detect the unstamped HEAD via SHA mismatch). Thepull_requestcheckjob is unchanged. Details: family-osdocs/repo-state/spec.md§2 / §4.Review
Batch of 13 caller bumps, one heterogeneous delta seat over the whole batch diff (the family-os#127 owner-approved lighter scheme for mechanical copies, cf. persona-engine#49). Seat record on caty-ai/family-os#163.
完了記録 (Completion record)
candidate SHA: f1beb66
implementer: Alpha (Claude Fable 5.1) — 2-line mechanical yml edit
reviewer: BATCH_SEAT
identity check: 別モデル
CI: see PR checks at merge time (recorded on family-os#163 per repo)
release: N/A ③ (CI wiring only — the caller 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 → 結果
repo-state.yml@v0.18.0andgenerator_ref: v0.18.0pushrun on main after merge refresheslatest_tagto this repo's live latest Releasestatus.jsondiffTracked in caty-ai/family-os#163.
🤖 Generated with Claude Code