Skip to content

ci: sync shared checker and notify parents on release - #11

Merged
sbokatuk merged 3 commits into
mainfrom
ci/drift-release-links
Jul 30, 2026
Merged

ci: sync shared checker and notify parents on release#11
sbokatuk merged 3 commits into
mainfrom
ci/drift-release-links

Conversation

@sbokatuk

Copy link
Copy Markdown
Owner

Two family-uniform changes:

  • build/check-upstream.sh synced verbatim with the family (new optional source manifest column; no behavioural change here — this manifest has no such rows).
  • release.yml now ends with a notify-parents job: build/notify-parents.sh files (or updates) a re-pin issue in each repository listed in build/parents.tsv, linking the release and its notes. Called explicitly because releases are created with GITHUB_TOKEN, whose events start no workflows. Silent no-op until the PARENT_ISSUE_PAT secret exists; prerelease tags notify nobody.

🤖 Generated with Claude Code

sbokatuk and others added 3 commits July 30, 2026 15:03
No behavioural change here - this manifest has no rows with the new
optional source column - keeping the checker verbatim with the family
per build/upstream.tsv's contract.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The parents pin these packages by exact version and would otherwise
learn about a release from their daily upstream-drift check the next
morning. release.yml's new final job calls notify-parents.yml, which
runs build/notify-parents.sh over build/parents.tsv: one issue per
pinning repository, linking the release and its notes; an open issue
asking for an older version is commented and retitled instead of
duplicated, and prerelease tags notify nobody.

Cross-repository issues cannot be written with GITHUB_TOKEN, so the
job authenticates with PARENT_ISSUE_PAT (fine-grained, Issues
read/write on the parent repositories only) and reports itself skipped
while that secret does not exist - releases never depend on it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The exact-title check used `gh issue list --search`, which rides the
search index - eventually consistent, so an issue filed seconds earlier
is invisible to it and a re-run files a duplicate (measured on a live
double-run, not theorised). The list endpoint is read-your-writes; the
title prefix match moves client-side.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@sbokatuk
sbokatuk deployed to nuget.org July 30, 2026 12:50 — with GitHub Actions Active
@sbokatuk
sbokatuk merged commit 669b025 into main Jul 30, 2026
7 checks passed
@sbokatuk
sbokatuk deleted the ci/drift-release-links branch July 30, 2026 13:13
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