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

chore: update dependency @spectrum-css/actionbutton to v7.0.0 #5035

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 17, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@spectrum-css/actionbutton (source) 7.0.0-s2-foundations.22 -> 7.0.0 age adoption passing confidence

Release Notes

adobe/spectrum-css (@​spectrum-css/actionbutton)

v7.0.0

Compare Source

Major Changes
  • #​2786 6c19fcf Thanks @​pfulton! - ## Breaking change

    This major update creates a bridge between the Spectrum 1 (S1) and Spectrum 2 (S2) designs, dubbed "Spectrum 2 Foundations". These do NOT reflect a fully migrated S2 component. This approach allows consumers to swap the appearance of their components between S1, Express, and S2 by leveraging a "system" layer that remaps the necessary component-level tokens to the appropriate token dataset.

    For these components to appear S2, you must load the assets with the @spectrum-css/tokens at v16 or higher.

    For S1 or Express, load assets with the @spectrum-css/tokens at v14.x or v15.x.

    If you are looking to implement a fully S2 design, please explore the next tag releases instead of using this foundations release. This release is used in Spectrum Web Components 1.x.

Deprecations

The metadata folder containing the mods.md and metadata.json assets has been removed from source. To find information about the components including what selectors, modifiers, and passthroughs are used, please see the dist/metadata.json asset shipped with every component containing CSS.

The index-vars.css asset has been removed in this release as it was previously deprecated and is no longer maintained. Please use the index.css or index-base.css

File usage

If you are rendering components and need only the S2 Foundations styles, you can make use of the index.css asset which contains all the base styles plus the system mappings for S2 Foundations.

If you are using this version to publish only an S1 or Express component, you can use the index-base.css plus the desired themes/(spectrum|express).css file.

To render a component that can be easily swapped between the S2 Foundations, S1, or Express contexts, load index-base.css with the index-theme.css file and leverage the appropriate context classes (.spectrum--legacy for S1 and .spectrum--express for Express).

Patch Changes

v7.0.0-s2-foundations.24

Compare Source

Major Changes
  • #​2786 f6ad55e Thanks @​pfulton! - feat: s2 foundations non-gray-800 colors update

    Property name Context Old value Updated value
    --spectrum-blue-800 dark rgb(69, 110, 254) rgb(64, 105, 253)
    --spectrum-red-800 dark rgb(230, 54, 35) rgb(223, 52, 34)
    --spectrum-orange-800 dark rgb(205, 86, 0) rgb(199, 82, 0)
    --spectrum-yellow-800 dark rgb(169, 110, 0) rgb(164, 106, 0)
    --spectrum-chartreuse-800 dark rgb(109, 131, 0) rgb(106, 127, 0)
    --spectrum-celery-800 dark rgb(69, 138, 19) rgb(66, 134, 18)
    --spectrum-green-800 dark rgb(6, 140, 82) rgb(6, 136, 80)
    --spectrum-seafoam-800 dark rgb(8, 138, 116) rgb(8, 134, 112)
    --spectrum-cyan-800 dark rgb(15, 128, 194) rgb(13, 125, 186)
    --spectrum-indigo-800 dark rgb(119, 97, 252) rgb(116, 91, 252)
    --spectrum-purple-800 dark rgb(161, 84, 229) rgb(157, 78, 228)
    --spectrum-fuchsia-800 dark rgb(192, 64, 212) rgb(186, 60, 206)
    --spectrum-magenta-800 dark rgb(231, 41, 105) rgb(224, 38, 101)
    --spectrum-pink-800 dark rgb(220, 47, 156) rgb(213, 45, 151)
    --spectrum-turqoise-800 dark rgb(9, 135, 147) rgb(9, 131, 142)
    --spectrum-brown-800 dark rgb(148, 118, 73) rgb(143, 114, 69)
    --spectrum-silver-800 dark rgb(123, 123, 123) rgb(118, 118, 118)
    --spectrum-cinnamon-800 dark rgb(179, 103, 64) rgb(176, 98, 59)
Patch Changes

v7.0.0-s2-foundations.23

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - "after 12pm on thursday" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner January 17, 2025 02:54
Copy link

changeset-bot bot commented Jan 17, 2025

⚠️ No Changeset found

Latest commit: 8515582

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/spectrum-css-actionbutton-7.x branch 2 times, most recently from 90cb988 to aded6e6 Compare January 22, 2025 10:29
@renovate renovate bot force-pushed the renovate/spectrum-css-actionbutton-7.x branch 14 times, most recently from e8f0071 to d9310fe Compare January 31, 2025 09:22
@renovate renovate bot force-pushed the renovate/spectrum-css-actionbutton-7.x branch from d9310fe to 8515582 Compare January 31, 2025 18:33
@renovate renovate bot changed the title chore: update dependency @spectrum-css/actionbutton to v7.0.0-s2-foundations.24 chore: update dependency @spectrum-css/actionbutton to v7.0.0 Jan 31, 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.

0 participants