Skip to content

feat: upgrade to brand evolution colors#31256

Merged
georgewrmarshall merged 2 commits intomainfrom
fix/design-tokens-v5.1.0
Mar 25, 2025
Merged

feat: upgrade to brand evolution colors#31256
georgewrmarshall merged 2 commits intomainfrom
fix/design-tokens-v5.1.0

Conversation

@georgewrmarshall
Copy link
Copy Markdown
Contributor

@georgewrmarshall georgewrmarshall commented Mar 25, 2025

Description

This PR updates the @metamask/design-tokens package from v5.0.0 to v5.1.0 to align with MetaMask's brand evolution color updates. The most notable change is the transition from our traditional blue to the new "blurple" color scheme, which can be seen in various UI components like toggle switches and interactive elements.

Key changes include:

  1. Updating primary/default colors to the new "blurple" palette:
    • Light mode (Blue500): #0376c9#4459ff
    • Dark mode(Blue300): #43aefc#8b99ff

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/4406

Manual testing steps

  1. Pull the branch and install dependencies
  2. Build and run the application locally: yarn start
  3. Verify the new "blurple" color scheme appears correctly in:
    • Toggle switches
    • Primary action buttons
    • Interactive elements
    • Light and dark mode
  4. Run Storybook to verify component appearances: yarn storybook
    • Specifically check the BannerAlert story for correct color implementation
  5. Ensure proper contrast ratios are maintained across all color updates

Screenshots/Recordings

Before

Reviewing current colors across the extension in light and dark theme

before720.mov

BanneAlert stories

sb.before720.mov

After

Reviewing brand evolution colors across the extension in light and dark theme

after720.mov

BanneAlert stories

sb.after720.mov

Pre-merge author checklist

  • I've followed MetaMask Contributor Docs
  • I've completed the PR template to the best of my ability
  • I've included tests if applicable
  • I've documented my code using JSDoc format if applicable
  • I've applied the right labels on the PR

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed)
  • I confirm that this PR addresses all acceptance criteria and includes the necessary testing evidence such as recordings and or screenshots

@georgewrmarshall georgewrmarshall added the team-design-system All issues relating to design system in Extension label Mar 25, 2025
@georgewrmarshall georgewrmarshall self-assigned this Mar 25, 2025
@github-actions
Copy link
Copy Markdown
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@metamaskbot metamaskbot added the INVALID-PR-TEMPLATE PR's body doesn't match template label Mar 25, 2025
@socket-security
Copy link
Copy Markdown

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@metamask/design-tokens@5.0.05.1.0 None 0 293 kB metamaskbot

View full report↗︎

Comment thread package.json
"@metamask/contract-metadata": "^2.5.0",
"@metamask/controller-utils": "^11.4.0",
"@metamask/design-tokens": "^5.0.0",
"@metamask/design-tokens": "^5.1.0",
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upgrading design tokens from V3 release of design system monrepo

@@ -63,7 +63,7 @@ exports[`IncomingTransactionToggle should render existing incoming transaction p
style="display: flex; width: 52px; align-items: center; justify-content: flex-start; position: relative; cursor: pointer; background-color: transparent; border: 0px; padding: 0px; user-select: none;"
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updating snapshots that use the Toggle button which uses the JS design tokens instead of the CSS variables

@georgewrmarshall georgewrmarshall marked this pull request as ready for review March 25, 2025 00:57
@georgewrmarshall georgewrmarshall requested a review from a team as a code owner March 25, 2025 00:57
@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [3b9d9e5]
Page Load Metrics (2523 ± 377 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint177937872412690332
domContentLoaded166233302189545262
load179342162523785377
domInteractive27124532713
backgroundConnect481498355394189
firstReactRender22231835024
getState2747514213565
initialActions00000
loadScripts123526731556384185
setupStore10344779747
uiStartup216813043470532571564
Bundle size diffs
  • background: 0 Bytes (0.00%)
  • ui: 0 Bytes (0.00%)
  • common: 0 Bytes (0.00%)

@georgewrmarshall georgewrmarshall added this pull request to the merge queue Mar 25, 2025
Merged via the queue into main with commit 2d3d27e Mar 25, 2025
121 checks passed
@georgewrmarshall georgewrmarshall deleted the fix/design-tokens-v5.1.0 branch March 25, 2025 18:47
@github-actions github-actions Bot locked and limited conversation to collaborators Mar 25, 2025
@metamaskbot metamaskbot added the release-12.16.0 Issue or pull request that will be included in release 12.16.0 label Mar 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

INVALID-PR-TEMPLATE PR's body doesn't match template release-12.16.0 Issue or pull request that will be included in release 12.16.0 team-design-system All issues relating to design system in Extension

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants