chore: bump uuid from ^8.3.2 to ^9.0.1 - #10117
Merged
Merged
Conversation
cryptodev-2s
temporarily deployed
to
default-branch
September 4, 2026 15:18 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Contributor
Author
|
@metamaskbot update-changelogs |
cryptodev-2s
changed the title
^8.3.2 to ^9.0.1uuid from ^8.3.2 to ^9.0.1
cryptodev-2s
force-pushed
the
chore/bump-uuid-9.0.1
branch
from
September 4, 2026 15:19
43cb170 to
709a27a
Compare
This comment has been minimized.
This comment has been minimized.
cryptodev-2s
force-pushed
the
chore/bump-uuid-9.0.1
branch
from
September 4, 2026 15:25
709a27a to
df499fe
Compare
Contributor
Author
|
@metamaskbot update-changelogs |
This comment has been minimized.
This comment has been minimized.
cryptodev-2s
force-pushed
the
chore/bump-uuid-9.0.1
branch
2 times, most recently
from
September 9, 2026 19:30
c9287eb to
a5c29b6
Compare
Contributor
Author
|
@metamaskbot update-changelogs |
This comment has been minimized.
This comment has been minimized.
cryptodev-2s
enabled auto-merge
September 9, 2026 19:35
cryptodev-2s
force-pushed
the
chore/bump-uuid-9.0.1
branch
from
September 9, 2026 20:00
1f378b2 to
9c6b5b9
Compare
Contributor
Author
|
@metamaskbot update-changelogs |
Contributor
|
✅ Changelogs updated and pushed. |
Mrtenz
approved these changes
Sep 9, 2026
Merged
3 of 4 tasks
pull Bot
pushed a commit
to Reality2byte/core
that referenced
this pull request
Sep 18, 2026
## Explanation Creates monorepo release 1265.0.0 with one package release: - `@metamask/analytics-controller` 3.1.0 This release ships independent marketing consent and purpose-aware event classification. It adds `optedInToMarketing`, `optInToMarketing` / `optOutOfMarketing` / `resetMarketingConsentDecision`, and a persisted `eventsConfig` whose unlisted events default to product-only. Named `track` and `view` payloads are delivered once with their allowed purposes in `context.consent.categoryPreferences` and their capture-time config version in `context.eventsConfigVersion`. Queues and fragments retain capture-time purpose classification so config changes cannot reclassify captured events. Mixed-purpose fragments classify each declared lifecycle event independently. Workspace dependents `@metamask/network-controller` and `@metamask/wallet-cli` are aligned to `@metamask/analytics-controller` `^3.1.0`. The release also includes pending dependency bumps for `uuid` (`^8.3.2` → `^11.1.1`) and `@metamask/utils` (`^11.12.0` → `^12.0.0`). ## References - MetaMask#10232 - MetaMask#10117 - MetaMask#10243 - MetaMask#10192 ## Checklist - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [x] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them Made with [Cursor](https://cursor.com) --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>
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
References
Checklist
Note
Low Risk
Dependency-only major bump with no source edits; risk is mainly if uuid v9 behavior or bundling differs from v8 in downstream clients, though usage here is standard
v4generation.Overview
This PR standardizes the monorepo on
uuidv9 by bumpinguuidfrom^8.3.2to^9.0.1in the root devDependencies and across many@metamask/*packages that depend on it directly.Where packages typed against UUIDs,
@types/uuidis updated from^8.3.0to^9.0.8, and the lockfile drops the old@types/uuid@^8.3.0entry. Affected packages record the bump under[Unreleased]in their changelogs; there are no runtime or import changes in this diff—existingv4ESM imports stay as-is.Reviewed by Cursor Bugbot for commit 93c51bd. Bugbot is set up for automated code reviews on this repo. Configure here.