revert: un-release 9.0.0 - #423
Merged
Merged
Conversation
The 9.0.0 release (#420) was never published to npm because the team decided to migrate publishing to OIDC trusted publishing first. Revert the version bump so 9.0.0 can be re-cut cleanly after the OIDC migration. - package.json: 9.0.0 -> 8.2.0 - CHANGELOG.md: remove the [9.0.0] section heading and fold its entries (#419, #410) back under [Unreleased]; reset the [Unreleased] compare link to v8.2.0...HEAD and drop the [9.0.0] link. The Node.js 18/20 drop entry (#422), added after 9.0.0 was cut, is kept under [Unreleased].
OGPoyraz
marked this pull request as draft
August 26, 2026 10:38
OGPoyraz
marked this pull request as ready for review
August 26, 2026 10:39
OGPoyraz
enabled auto-merge (squash)
August 26, 2026 10:43
Mrtenz
approved these changes
Aug 26, 2026
OGPoyraz
added a commit
that referenced
this pull request
Aug 26, 2026
The release PR was created by the action-create-release-pr workflow, which formats CHANGELOG.md with Prettier v3 (a blank line after every heading). This repo uses Prettier v2, whose auto-changelog validation (run in CI via `yarn auto-changelog validate --rc` on release branches) rejects that format. - Reformat CHANGELOG.md to the repo's Prettier v2 style (matching main) so the changelog validation passes. - Remove the auto-generated `### Uncategorized` entries (#423 un-release, the #420 release commit, and the #411 CI chore), which are internal and not user-facing. The user-facing changes remain under `### Changed`.
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
2 participants
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.
Explanation
The
9.0.0release (#420) was tagged but never published to npm — the team decided to migrate publishing to OIDC trusted publishing (#421) before cutting the release. This PR un-releases9.0.0so it can be re-cut cleanly on top of the OIDC migration.Changes
package.json:9.0.0→8.2.0.CHANGELOG.md:## [9.0.0]section heading and fold its entries back under## [Unreleased]:boolvalues insignTypedData(#419)[Unreleased]compare link tov8.2.0...HEADand drop the[9.0.0]link.The Node.js 18/20 drop entry (#422), which was added after
9.0.0was cut, is preserved under[Unreleased].Follow-ups (not in this PR)
v9.0.0git tag (646b724) will be deleted separately before the newrelease/9.0.0PR (npm was never published, so nothing to unpublish).release/9.0.0PR will be created via the standard release workflow.References