Release 1184.0.0

[tuna1207]

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.3 → 6.0.0
@metamask/subscription-controller	6.2.2 → 7.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.4 → 0.6.0
@metamask/wallet	9.0.0 → 9.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

High Risk
Bundles multiple breaking majors (shield, subscription, wallet) that change messenger wiring and initialization; consumers must align upgrades and avoid duplicate controller/service registration.

Overview
Cuts monorepo release 1184.0.0 by bumping package versions, refreshing changelogs, and updating yarn.lock / dependency ranges—no application code changes in this diff.

@metamask/shield-controller@6.0.0 and @metamask/subscription-controller@7.0.0 ship as major releases (messenger-backed API services and breaking controller options, as documented in their changelogs). @metamask/claims-controller@0.6.0 is a minor bump for the BaseDataService migration. @metamask/wallet@10.0.0 is a major release that pulls in those versions and documents breaking default wiring for Claims, Shield, and Subscription; @metamask/wallet-cli only updates its @metamask/wallet dependency to ^10.0.0.

^{Reviewed by Cursor Bugbot for commit f609277. Bugbot is set up for automated code reviews on this repo. Configure here.}

[metamask-ci]

✅ No changelog changes needed.

[tuna1207]

@metamaskbot publish-previews

[FrederikBolding]

These should still be marked as breaking IMO as they require changes on the client plumbing for the bump.

[tuna1207]

Agree, updated in f23e3ef

[FrederikBolding]

If we are using this in production perhaps now would be a good time to go to 1.0.0?

[tuna1207]

We can keep this at 0.6.0 for now since there are no breaking changes in this release — happy to bump to 1.0.0 in a follow-up once we're ready to declare the API stable.

[tuna1207]

I think we can keep this at 0.6.0 for now since there are no breaking changes in this release — happy to bump to 1.0.0 in a follow-up once we're ready to declare the API stable.

[FrederikBolding]

This shouldn't be removed, but feel free to move it below the breaking changes.