Skip to content

Release 1184.0.0 - #9809

Open
tuna1207 wants to merge 4 commits into
mainfrom
release/1184.0.0
Open

Release 1184.0.0#9809
tuna1207 wants to merge 4 commits into
mainfrom
release/1184.0.0

Conversation

@tuna1207

@tuna1207 tuna1207 commented Aug 8, 2026

Copy link
Copy Markdown
Member

Explanation

Release 1184.0.0 with major bumps for Shield and Subscription controllers, and minor bumps for Claims and Wallet.

Major

Package Version
@metamask/shield-controller 5.1.36.0.0
@metamask/subscription-controller 6.2.27.0.0

@metamask/shield-controller@6.0.0

  • BREAKING: Replace ShieldRemoteBackend / createShieldRemoteBackend with messenger-backed ShieldApiService
  • BREAKING: Remove backend from ShieldControllerOptions and related backend exports
  • BREAKING: Controller now uses ShieldApiService:* actions instead of AuthenticationController:getBearerToken

@metamask/subscription-controller@7.0.0

  • BREAKING: Move subscription API access behind messenger-backed SubscriptionService (BaseDataService)
  • BREAKING: SubscriptionController no longer constructs/accepts a SubscriptionService instance; options are { messenger, state?, pollingInterval? } only
  • Removes SubscriptionControllerServiceOptions, SubscriptionServiceConfig, and direct auth construction

Minor

Package Version
@metamask/claims-controller 0.5.40.6.0
@metamask/wallet 9.0.09.1.0

@metamask/claims-controller@0.6.0

  • Migrate ClaimsService to BaseDataService with caching/policy/validation
  • Export ClaimsControllerOptions, ClaimsServiceConfig, and related action/event types
  • fetchFunction optional (defaults to globalThis.fetch)

@metamask/wallet@9.1.0

  • Wire ClaimsService / ClaimsController, ShieldController / ShieldApiService, and SubscriptionController / SubscriptionService into default wallet initialization
  • Add optional instanceOptions.remoteFeatureFlagController.defaultFeatureFlags
  • Bump deps to the new claims/shield/subscription versions

Other

  • @metamask/wallet-cli dependency bump only (@metamask/wallet ^9.0.0^9.1.0); not a separate package release

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Medium Risk
The release bundles major breaking API changes in shield and subscription controllers and documents auth-dependent wallet wiring; consumers must upgrade messenger/service integration, not just semver ranges.

Overview
Release 1184.0.0 cuts published versions and changelog entries only—no new runtime code in this diff.

The monorepo root moves 1183.0.0 → 1184.0.0. @metamask/claims-controller is released at 0.6.0 (documents prior ClaimsService / BaseDataService work). @metamask/shield-controller and @metamask/subscription-controller ship 6.0.0 and 7.0.0 with breaking messenger/service refactors documented in their changelogs. @metamask/wallet goes 9.0.0 → 9.1.0, bumps those three controllers in package.json, and records wiring plus optional defaultFeatureFlags. @metamask/wallet-cli only updates its @metamask/wallet dependency to ^9.1.0 and the changelog line; yarn.lock tracks the new version ranges.

Reviewed by Cursor Bugbot for commit d74e69d. Bugbot is set up for automated code reviews on this repo. Configure here.

@tuna1207
tuna1207 marked this pull request as ready for review August 8, 2026 12:20
@tuna1207
tuna1207 requested review from a team as code owners August 8, 2026 12:20
@tuna1207
tuna1207 deployed to default-branch August 8, 2026 12:21 — with GitHub Actions Active
@metamask-ci

metamask-ci Bot commented Aug 8, 2026

Copy link
Copy Markdown

✅ No changelog changes needed.

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.

3 participants