Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update @automattic/color-studio package to version 4.1.0 #99037

Closed
wants to merge 1 commit into from

Conversation

ciampo
Copy link
Contributor

@ciampo ciampo commented Jan 29, 2025

Related to #98732 (comment)

Proposed Changes

Update @automattic/color-studio package to the current latest version (4.1.0) across all packages in the repository

Why are these changes being made?

This allows the project to consume the updated shades of blue released with version 4.0.1

Testing Instructions

Looking at the CHANGELOG, it looks like there are 2 main changes affecting the web version when updating from 3.0.1 to 4.1.0:

This will affect the colors all over the repository, and therefore we should smoke test as many pages in as many environments as possible!

Pre-merge Checklist

  • Has the general commit checklist been followed? (PCYsg-hS-p2)
  • Have you written new tests for your changes?
  • Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
  • Have you checked for TypeScript, React or other console errors?
  • Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
  • Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
    • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
  • For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

@ciampo ciampo self-assigned this Jan 29, 2025
@ciampo ciampo requested a review from a team as a code owner January 29, 2025 13:05
@matticbot matticbot added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Jan 29, 2025
@matticbot
Copy link
Contributor

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

  • blaze-dashboard
  • command-palette-wp-admin
  • happy-blocks
  • help-center
  • notifications
  • odyssey-stats
  • whats-new
  • wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/color-studio-package-4-0-1 on your sandbox.

@ciampo ciampo force-pushed the update/color-studio-package-4-0-1 branch from ae72312 to bfaae2d Compare January 29, 2025 13:05
@matticbot
Copy link
Contributor

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

@ciampo
Copy link
Contributor Author

ciampo commented Jan 29, 2025

Ah, I see that #99033 has already been opened with similar changes — I hadn't seen any mention of the PR in related conversations and that's why I went ahead and opened this one.

Folks, feel free to close this PR if you think that #99033 should be the place where to make the update.

@ciampo ciampo closed this Jan 29, 2025
@github-actions github-actions bot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Jan 29, 2025
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.

2 participants