Skip to content

Add changelog validate-onboarding for Prestage registration drift - #3855

Open
cotti wants to merge 4 commits into
feature/products-release-notes-pathfrom
feature/release-notes-onboarding-validation
Open

Add changelog validate-onboarding for Prestage registration drift#3855
cotti wants to merge 4 commits into
feature/products-release-notes-pathfrom
feature/release-notes-onboarding-validation

Conversation

@cotti

@cotti cotti commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Why

A product registered as features.release-notes: prestage whose repository lacks the Prestage scaffolding would silently be skipped by the Prestage Release Orchestrator — or fail at feature freeze, the worst possible moment. Registration drift needs to be CI-gateable (RFC B4, docs-eng-team#698).

What

New docs-builder changelog validate-onboarding command: for every Prestage-registered product it probes the repository (resolved from the product key or its repository: override) via the GitHub contents API for the changelog configuration (docs/changelog.yml or root changelog.yml) and the changelog-validate/changelog-submit/changelog-upload/changelog-bundle-stage workflows, emitting one actionable error per product with the missing files and exiting non-zero. Unreadable repositories (bad credentials, rate limiting) fail the run rather than passing it vacuously. Uses the shared GitHubApiTransport, so the whole thing is covered by fake-HTTP tests.

Stack: 2/5 — depends on the features.release-notes path values (#3854).

@cotti
cotti requested review from a team as code owners August 13, 2026 11:40
@cotti
cotti requested a review from Mpdreamz August 13, 2026 11:40
@cotti cotti added the feature label Aug 13, 2026
@cotti
cotti force-pushed the feature/release-notes-onboarding-validation branch from d26f390 to 025a4f7 Compare August 13, 2026 12:48
A product registered as features.release-notes: prestage without the
Prestage scaffolding in its repository would silently be skipped by the
Prestage Release Orchestrator or fail at feature freeze. The new command
probes each Prestage product's repository (contents API) for the
changelog configuration and the validate/submit/upload/bundle-stage
workflows, exiting non-zero on drift so CI can gate on it (RFC B4,
docs-eng-team#698).

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants