docs: prep release v0.9.0#754
Merged
Merged
Conversation
Adds the dated release-notes file (.github/release-notes-20260529.md) so the upcoming develop → main cut produces a tagged v0.9.0 GitHub Release with curated user-facing notes. ~97 changesets have accumulated on develop since v0.8.0. The highest fixed-pair bump is minor, so both packages go 0.8.0 → 0.9.0 in fixed mode. The release is API-contract heavy: 5 breaking changes to /api/v1/* (RFC 7807 envelope, lowercase_snake_case codes, GUID-only version writes, RFC 8594 deprecation headers, ownerId removal) — all pre-1.0 minor bumps per convention. Notes follow the template: 6-12 word product-level bullets, breaking changes flagged, purely-technical items collapsed into the trailing bucket per section. All three sections present, no (write here) placeholder — check-release-notes.yml will pass. Closes #753.
check-changeset.yml requires every develop PR to carry a changeset. This release-prep PR is docs/CI-only, so it ships an empty changeset (no package bump) — same pattern as the v0.8.0 prep PR (#556). The actual version bump is declared by the ~97 feature changesets already on develop.
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.
Closes #753.
Adds the dated release-notes file (
.github/release-notes-20260529.md) so the upcomingdevelop → maincut produces a tagged v0.9.0 Release with curated user-facing notes.~97 changesets have accumulated on develop since v0.8.0. Highest fixed-pair bump is minor, so both packages go
0.8.0 → 0.9.0in fixed mode. The release is API-contract heavy — 5 breaking changes to/api/v1/*(RFC 7807 envelope,lowercase_snake_casecodes, GUID-only version writes, RFC 8594 deprecation headers,ownerIdremoval), all pre-1.0 minor bumps per convention.Test plan
release-notes-20260529.mdis lexically greater than the prior latest (20260516.md), so the release workflow picks this file.## Fixed/## New Feature/## Changed) present; no(write here)placeholders —check-release-notes.ymlwill pass.