Skip to content

gate: fail when a GA'd major's release page still describes itself as a pre-release (v16+)#8950

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-project-manager merged 1 commit into from
Aug 16, 2026
+900 −0
Merged

gate: fail when a GA'd major's release page still describes itself as a pre-release (v16+) #8950

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .github/workflows/lint.yml
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -540,6 +540,18 @@ jobs:
- name: Release-notes drift guard
run: pnpm check:release-notes

# Release-page STATUS guard (#8892). The guard above proves a released
# major has a page; it never reads what the page SAYS. Both of the last
# two GA cuts shipped a page still describing itself as a pre-release —
# v17 for a day ("the train is preparing to ship"), v16 for three weeks
# ("currently published as 16.0.0-rc.0") — with CI fully green each time,
# found only because a human read the page. This asserts that for every
# GA'd major from v16 on, the status blockquote and the index entry both
# describe a shipped release. Scoped to v16+ by maintainer ruling; the
# gate prints that cutoff and its reason on both the OK and failure paths.
- name: Release-page status guard
run: pnpm check:release-page-status

# Release-body limit guard (#4900). The GitHub Releases API rejects any
# body over 125,000 characters, and @objectstack/spec's changelog section
# for one v17 RC is ~343,000 — so the release step 422'd after npm had
Expand Down
1 change: 1 addition & 0 deletions package.json
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -79,6 +79,7 @@
"check:changeset-gate-self-tests": "node scripts/check-empty-changeset.mjs --self-test && node scripts/check-adr-0087-registration.mjs --self-test && node scripts/check-changeset-no-major.mjs --self-test",
"check:override-consistency": "node scripts/check-override-consistency.mjs --self-test && node scripts/check-override-consistency.mjs",
"check:release-notes": "node scripts/check-release-notes.mjs",
"check:release-page-status": "node scripts/check-release-page-status.mjs --self-test && node scripts/check-release-page-status.mjs",
"check:release-body": "node scripts/release-github-releases.mjs --self-test",
"check:node-version": "node scripts/check-node-version.mjs",
"check:workflow-status-functions": "node scripts/check-workflow-status-functions.mjs --self-test && node scripts/check-workflow-status-functions.mjs",
Expand Down
Loading
Loading