Skip to content

9.0.0 - #420

Merged
OGPoyraz merged 2 commits into
mainfrom
release/9.0.0
Aug 25, 2026
Merged

9.0.0#420
OGPoyraz merged 2 commits into
mainfrom
release/9.0.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This is the release candidate for version 9.0.0.

@OGPoyraz
OGPoyraz marked this pull request as ready for review August 25, 2026 07:51
@OGPoyraz
OGPoyraz merged commit 646b724 into main Aug 25, 2026
19 of 20 checks passed
@OGPoyraz
OGPoyraz deleted the release/9.0.0 branch August 25, 2026 08:51
OGPoyraz added a commit that referenced this pull request Aug 26, 2026
## Explanation

The `9.0.0` release
([#420](#420)) was tagged
but **never published to npm** — the team decided to migrate publishing
to OIDC trusted publishing
([#421](#421)) before
cutting the release. This PR un-releases `9.0.0` so it can be re-cut
cleanly on top of the OIDC migration.

## Changes

- **`package.json`**: `9.0.0` → `8.2.0`.
- **`CHANGELOG.md`**:
- Remove the `## [9.0.0]` section heading and fold its entries back
under `## [Unreleased]`:
- **BREAKING**: Reject ambiguous `bool` values in `signTypedData`
([#419](#419))
- Add additional validation to EIP7702 methods
([#410](#410))
- 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](#422)), which was
added after `9.0.0` was cut, is preserved under `[Unreleased]`.

## Follow-ups (not in this PR)

- The existing `v9.0.0` **git tag** (`646b724`) will be deleted
separately before the new `release/9.0.0` PR (npm was never published,
so nothing to unpublish).
- After this merges, a fresh `release/9.0.0` PR will be created via the
standard release workflow.

## References

- Reverts the release portion of #420
- Depends on OIDC migration #421 (merged)
@OGPoyraz OGPoyraz mentioned this pull request Aug 26, 2026
4 tasks
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`.
OGPoyraz added a commit that referenced this pull request Aug 26, 2026
Remove the auto-generated `### Uncategorized` entries (the #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`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants