chore: reset published spec baseline#9
Merged
Conversation
Retire the under-annotated seed baseline and its noisy correction diff. Re-publish from the accurate producer spec so the first published release is a clean baseline (publish.ts emits 'Initial published spec.' when no prior spec exists).
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
1 participant
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
The first real
publish-openapirun cutv1.12+20260617.86e6d5d, but its changelog/release notes are a raw oasdiff diff against the under-annotated seed baseline (v1.12+20260610.28cae0f, a manual seed). On this public hub that reads as a wall of breaking API changes (new required fields, type changes, new path params) when in fact the runtime API never changed, these are spec-accuracy corrections.What this does
Resets the hub to a pristine state so we can re-publish the accurate spec as a clean baseline:
spec/openapi.json,spec/openapi.yaml,spec/provenance.jsonCHANGELOG.mdto its headerFollow-up (not in this PR)
After merge: delete the two existing GitHub releases + tags, then redrive the production pipeline. With no prior spec on disk,
publish.tstakes the first-publish path and emitsInitial published spec., producing a single clean baseline release with no misleading breaking-change dump.