feat: update changelog to prep release#178
Merged
Merged
Conversation
owencraston
approved these changes
May 6, 2026
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
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.
Summary
Adds a changelog entry to
packages/siteso the next release publishes a new site version aligned with@metamask/snap-simple-keyring-snap@2.1.0.Why
The site embeds the snap's
package.jsonversion at build time:When v2.1.0 of the snap was released in #177, the release tool only bumped the snap package because only
packages/snap/CHANGELOG.mdhad## [Unreleased]entries. The site stayed at 2.0.1 on npm and still asks consumers to install snap v2.0.1 — which doesn't have the newkeyring_setSelectedAccounts/keyring_resolveAccountAddressmethods that@metamask/eth-snap-keyring@^22now invokes.This breaks the
metamask-extensione2e suite for any flow that installs SSK via the companion site (create-snap-account,create-remove-account-snap,snap-account-contract-interaction, etc.) because the local site dependency resolves to v2.0.1 and the install never matches the v2.1.0 snap fixture.Adding a
## [Unreleased]entry topackages/site/CHANGELOG.mdmakes the next release tool run bump and publish a new site version, while leaving the snap untouched (so no snap-registry allowlist update is required).Changes
packages/site/CHANGELOG.md: new### Changedentry under## [Unreleased]describing the bundled snap version reference bump.Follow-ups
Create Release Pull Requestworkflow. The tool will bump and publish only the site; the snap stays at 2.1.0.metamask-extension#42334, bump@metamask/snap-simple-keyring-siteto the new version. No snap fixture changes are needed, the new site bundle still references snap v2.1.0.Note
Low Risk
Documentation-only change in
packages/site/CHANGELOG.mdto trigger a site republish; no runtime or dependency code is modified.Overview
Prepares the next
@metamask/snap-simple-keyring-siterelease by adding an Unreleased changelog entry noting the bundled snap version reference bump from@metamask/snap-simple-keyring-snap@2.0.1to2.1.0, ensuring consumers install the updated snap via the dapp.Reviewed by Cursor Bugbot for commit 517457f. Bugbot is set up for automated code reviews on this repo. Configure here.