feat(swatch+swatchgroup): S2 migration #3677

cdransf · 2025-04-17T19:47:59Z

Description

CSS-1026 + CSS-1029

This migrates the swatch and swatchgroup components to S2. Custom properties have been remapped and added per the design specification.

An Add Swatch variant has been added with the required color tokens and the specified add UI icon.

Removed custom properties

--spectrum-swatch-border-color
--spectrum-swatch-dash-icon-color

New custom properties

--spectrum-swatch-border-color-rgb
--spectrum-swatch-border-opacity
--spectrum-corner-radius-full
--spectrum-corner-radius-none
--spectrum-swatch-disabled-icon-border-opacity
--spectrum-swatch-icon-color
--spectrum-swatch-rectangle-width-multiplier

New mods

--mod-add-button-background
--mod-add-button-background-down
--mod-add-button-background-hover
--mod-add-button-background-keyboard-focus
--mod-corner-radius-full
--mod-mixed-button-background
--mod-swatch-border-color-rgb
--mod-swatch-border-opacity

How and where has this been tested?

Please tag yourself on the tests you've marked complete to confirm the tests have been run by someone other than the author.

Validation steps

Regression testing

Validate:

The documentation pages for at least two other components are still loading, including:

The pages render correctly, are accessible, and are responsive.

If components have been modified, VRTs have been run on this branch:

VRTs have been run and looked at.
Any VRT changes have been accepted (by reviewer and/or PR author), or there are no changes.

Screenshots

To-do list

I have read the contribution guidelines.
I have updated relevant storybook stories and templates.
I have tested these changes in Windows High Contrast mode.
If my change impacts other components, I have tested to make sure they don't break.
If my change impacts documentation, I have updated the documentation accordingly.
✨ This pull request is ready to merge. ✨

changeset-bot · 2025-04-17T19:48:03Z

🦋 Changeset detected

Latest commit: 343a87b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@spectrum-css/swatchgroup	Major
@spectrum-css/swatch	Major

Not sure what this means? Click here to learn what changesets are.

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

github-actions · 2025-04-17T19:53:22Z

🚀 Deployed on https://pr-3677--spectrum-css.netlify.app

github-actions · 2025-04-17T19:58:26Z

File metrics

Summary

Total size: 1.38 MB^*
Total change (Δ): 🔴 ⬆ 0.97 KB (0.07%)

Table reports on changes to a package's main file. Other changes can be found in the collapsed Details section below.

Package	Size	Minified	Gzipped	Δ
swatch	12.60 KB	11.87 KB	2.10 KB	🔴 ⬆ 2.31 KB
swatchgroup	1.14 KB	1.10 KB	0.56 KB	🟢 ⬇ 0.08 KB

File change details

swatch

Filename	Head	Minified	Gzipped	Compared to base
index.css	12.60 KB	11.87 KB	2.10 KB	🔴 ⬆ 2.31 KB
metadata.json	6.81 KB	-	-	🔴 ⬆ 1.43 KB

swatchgroup

Filename	Head	Minified	Gzipped	Compared to base
index.css	1.14 KB	1.10 KB	0.56 KB	🟢 ⬇ 0.08 KB
metadata.json	0.51 KB	-	-	🔴 ⬆ < 0.01 KB

tokens

Filename	Head	Minified	Gzipped	Compared to base
css/dark-vars.css	46.87 KB	-	-	🔴 ⬆ 0.24 KB
css/global-vars.css	76.23 KB	-	-	-
css/index.css	250.83 KB	-	-	🔴 ⬆ 0.50 KB
css/large-vars.css	41.25 KB	-	-	-
css/light-vars.css	46.86 KB	-	-	🔴 ⬆ 0.24 KB
css/medium-vars.css	41.37 KB	-	-	-
json/tokens.json	388.37 KB	-	-	-

* Size is the sum of all main files for packages in the library.
* An ASCII character in UTF-8 is 8 bits or 1 byte.

rise-erpelding

Hi! This looks like a pretty minor migration but I have a few comments that I added below that I'll summarize:

Would love to see some updated testing options to show variants/states that we aren't seeing, this really helps us prevent regressions (or will once we have these changes in our main branch). Key-focus state was one that I mentioned to add, but it's also helpful to run through these manually too (like for instance, a hover test case usually shouldn't have a hover state, key-focus states shouldn't have an additional key focus state when you tab to the component).
I think by default we should be seeing some rounding on the swatch, although it's really still unclear to me after looking through specs whether or not the no-rounding option should still exist in S2. Some clarification from design on that might be good here, but doesn't need to be a blocker, but in the mean time since all the default swatches in the specs have rounding, ours should too.
Swatch group spacing for spacious maybe needs adjusting.

I have a couple of other questions after looking through the spec and the PR too:

Down state is kind of mentioned in the spec, but no tokens are referenced. Does this mean that swatch gets a down state treatment (with the perspective-based transform)? Not a blocker for this PR but we should find out.
Is that swatch border color (default) correct? I'm seeing it compute to rgba(19, 19, 19, 0.42) but the spec says gray-1000 which should be 0, 0, 0. If we adjust that though is there a difference between that default border and the light border?

I didn't check WHCM on this pass, but will plan to in the future!

rise-erpelding · 2025-04-24T00:41:33Z

components/swatch/index.css

 	&,
 	&::before,
 	&::after,
 	.spectrum-Swatch-fill,
 	.spectrum-Swatch-fill::before,
 	&.is-selected .spectrum-Swatch-fill,
 	&.is-selected .spectrum-Swatch-fill::before {
-		border-radius: 0;
+		border-radius: var(--mod-swatch-border-radius, var(--spectrum-corner-radius-75));


Is there a reason why this was replaced with partial rounding? The design changelog seems to indicate that the "no rounding" option has been removed for S2, but both the token and desktop specs indicate that it seems to be sticking around. Either way, the default version of the swatch should have this spec'd corner radius 75 rather than corner-radius-none.

There isn't (at least not a good one) I was just confused by the indication that no rounding was gone, partial was staying and what the default should be. I changed none as a variant and partial as the default. ✨

rise-erpelding · 2025-04-24T01:35:25Z

components/swatch/stories/swatch.test.js

Covering the add swatch here is good! After looking at the spec, I'm wondering if there are a few more improvements we could add to be more thorough, including, but maybe not limited to:

Key focused states

Looks like hover, active, and keyfocus have color changes for the add button variant, so showing those would be nice

Possibly disabled icons in different sizes so we know the size of the icon is changing appropriately

Awesome! I just updated the tests and stories. The add section of the testing grid also has active and hoer states.

The disabled icon sizes are shown in the docs by adjusting the sizes (as is the case with the add icon) — the icon size also reacts to the size control in Storybook. ✨

rise-erpelding · 2025-04-24T01:39:56Z

components/swatch/index.css

+	&.is-keyboardFocused,
+	&:focus-visible {
+		outline: var(--mod-swatch-focus-indicator-thickness, var(--spectrum-swatch-focus-indicator-thickness)) solid var(--mod-swatch-focus-indicator-color, var(--spectrum-swatch-focus-indicator-color));
+		outline-offset: var(--mod-swatch-focus-indicator-gap, var(--spectrum-swatch-focus-indicator-gap));
+	}


I'm capturing this focus indicator looking a little weird:

It works fine with the keyboard focused control in Storybook, but this happens when I focus with my keyboard.

Huh! I couldn't reproduce this one when focusing — it may be due to me testing after swapping the default rounding states from none to partial? ✨

Yep, that definitely helps!

I'm still seeing a very slight, slight difference when key focusing the is-keyboard-focused swatch (or toggling :is-focus-visible on and off), the video below will show that if it works for you.

My best guess is that this is happening because we have the outline focus treatment and also the ::after focus indicator (around L220), we should pick one or the other. Note that the ::after has a transition on the opacity to make it look a little smoother when it's key-focused, if we use the outline instead we'd probably want to do the same where a transition effect is placed on the opacity of the outline (I'm guessing from playing with it briefly that there might be a distinction between putting a transition on outline vs. putting it on the outline-color).

It would also be nice to make the focus control toggle on/off when we use the keyboard to focus/remove focus! For example, with button.

Screen.Recording.2025-04-28.at.9.22.36.AM.mov

rise-erpelding · 2025-04-24T01:42:10Z

components/swatchgroup/index.css

 }

 /* Spacious */
 .spectrum-SwatchGroup--spacious {
-	--mod-swatchgroup-spacing-regular: var(--mod-swatchgroup-spacing-spacious);
-	--spectrum-swatchgroup-spacing: var(--spectrum-spacing-100);
+	--mod-swatchgroup-spacing: var(--mod-swatch-group-spacing-spacious, var(--spectrum-swatch-group-spacing-spacious));


Looking at the spec, the spacing for spacious appears to use this token for xs and s, but is different (and not specific to swatch group) for m and l, should that be implemented here?

I added a mediumLarge variant since the spacing for those two are the same. I did drop compact as that's no longer present in the specs. I'm happy to restore it, but thought it might best be removed.

Sizing is typically not done with these kinds of selectors. I think we should try to stick with the t-shirt sizing conventions and just list the selectors for sizeM and sizeL for the same styles. They might be the same today but that doesn't mean they'll stay that way.

components/swatch/stories/swatch.stories.js

castastrophe

Looking good! My biggest feedback note is about the sizing for Swatch Group. Danke!

.changeset/proud-schools-reply.md

components/swatch/index.css

castastrophe · 2025-04-24T18:10:04Z

components/swatchgroup/index.css

 }

 /* Spacious */
 .spectrum-SwatchGroup--spacious {
-	--mod-swatchgroup-spacing-regular: var(--mod-swatchgroup-spacing-spacious);
-	--spectrum-swatchgroup-spacing: var(--spectrum-spacing-100);
+	--mod-swatchgroup-spacing: var(--mod-swatch-group-spacing-spacious, var(--spectrum-swatch-group-spacing-spacious));


Sizing is typically not done with these kinds of selectors. I think we should try to stick with the t-shirt sizing conventions and just list the selectors for sizeM and sizeL for the same styles. They might be the same today but that doesn't mean they'll stay that way.

components/swatchgroup/index.css

castastrophe · 2025-04-24T18:12:20Z

components/swatchgroup/stories/swatchgroup.stories.js

@@ -37,14 +31,18 @@ export default {
 		imageUrl: { table: { disable: true } },
 		isMixedValue: { table: { disable: true } },
 		gradient: { table: { disable: true } },
+		isKeyboardFocused: { table: { disable: true } },


Should we be importing and extending these settings directly from the Swatch story?

Good call! I totally missed that. I've updated the swatchgroup story to account for that. 🥳

Could we remove the disabled/selected controls on swatch group? Or define them if there is a reason to keep them.

rise-erpelding

Hiya, leaving another round of suggestions, the biggest issues I'm currently noticing are the doubled key-focus states and the swatch border tokens I mentioned in the comments.

rise-erpelding · 2025-04-28T14:50:42Z

components/swatch/index.css

+	&.is-keyboardFocused,
+	&:focus-visible {
+		outline: var(--mod-swatch-focus-indicator-thickness, var(--spectrum-swatch-focus-indicator-thickness)) solid var(--mod-swatch-focus-indicator-color, var(--spectrum-swatch-focus-indicator-color));
+		outline-offset: var(--mod-swatch-focus-indicator-gap, var(--spectrum-swatch-focus-indicator-gap));
+	}


Yep, that definitely helps!

I'm still seeing a very slight, slight difference when key focusing the is-keyboard-focused swatch (or toggling :is-focus-visible on and off), the video below will show that if it works for you.

My best guess is that this is happening because we have the outline focus treatment and also the ::after focus indicator (around L220), we should pick one or the other. Note that the ::after has a transition on the opacity to make it look a little smoother when it's key-focused, if we use the outline instead we'd probably want to do the same where a transition effect is placed on the opacity of the outline (I'm guessing from playing with it briefly that there might be a distinction between putting a transition on outline vs. putting it on the outline-color).

It would also be nice to make the focus control toggle on/off when we use the keyboard to focus/remove focus! For example, with button.

Screen.Recording.2025-04-28.at.9.22.36.AM.mov

rise-erpelding · 2025-04-28T14:59:06Z

components/swatch/stories/swatch.test.js

-			testHeading: "No rounding",
-			rounding: "none"


Do we still want to test no rounding here? Since it's still in the controls and we still have the .spectrum-Swatch--roundingNone class.

rise-erpelding · 2025-04-28T16:16:13Z

components/swatch/index.css

+.spectrum-Swatch--border {
+	.spectrum-Swatch-fill {
+		&::before {
+			box-shadow: inset 0 0 0 var(--spectrum-swatch-border-thickness) var(--mod-swatchgroup-border-color, var(--spectrum-swatchgroup-border-color));


It looks like this swatch border is gray-100/42% opacity now, which looks like it may be the same as the --lightBorder variant. Is there any reason to keep the light border variant (and its corresponding documentation) around then?

Light border:

(My understanding of swatch border colors is unfolding in real time). I'm realizing now that there are a few border color tokens:

From spectrum-tokens 13.3.0:
swatch-border-color: gray-1000
swatch-border-opacity: 42%
swatch-group-border-color: gray-1000
swatch-group-border-opacity: 20% - this doesn't seem to exist in spectrum-tokens

Then in custom tokens (this is light-vars) we also have these:

--spectrum-swatch-border-color: rgb(0 0 0 / 51%); --spectrum-swatch-border-color-light: rgb(0 0 0 / 42%); /** * `--spectrum-swatch-group-border-color` / `--spectrum-swatch-group-border-opacity` */ --spectrum-swatchgroup-border-color: rgb(255 255 255 / 20%);

And then as far as border colors, I'm aware that we previously had light colored borders for certain circumstances, I'm wondering if that's why we're seeing an option for 42% opacity and one for 20% opacity? Maybe? I was thinking before that maybe we ought to remove the light border variant, but now I'm on the fence. Either way, we should clean up the custom tokens to avoid some redundancy between the custom tokens and the tokens that we should have available already.

@rise-erpelding @cdransf Sorry to pop in here, but here's the PR where I left most of the discussion I had with Miruna about the light border stuff.

#2954

If I'm understanding Miruna's message correctly, the 42% border opacity (swatch-border-color) is for single swatches in S2, and then the 20% is for swatches in a swatch group in S2. I don't get the impression that design wants a "light border" option any longer, since Miruna also says: "we decided that for S2 we are gonna be more restrictive with this and give the guidance to have a border for single swatch or swatch group." Re-reading this, I understand her to say design wants all swatches in S2 to have a border, regardless of contrast (I think that's why the light border option existed, even though it was added inconsistently all over the place in a one-off fashion).

I have not reviewed this PR yet, but my instinct is that --spectrum-swatch-border-color (which has the S1 51% opacity in the snippet above) should actually be the 42% opacity for S2. The --spectrum-swatch-border-color-light custom variable (created for the light border option) can be removed. Something more along these lines:

--spectrum-swatch-border-color: rgba(0 0 0 / 42%); --sspectrum-swatchgroup-border-color: rgba(255 255 255 / 20%)

It's super confusing, so I'm happy to chat if I can clear anything up. We worked a lot out in that PR! ☝️

rise-erpelding · 2025-04-28T16:19:11Z

components/swatchgroup/stories/swatchgroup.stories.js

@@ -37,14 +31,18 @@ export default {
 		imageUrl: { table: { disable: true } },
 		isMixedValue: { table: { disable: true } },
 		gradient: { table: { disable: true } },
+		isKeyboardFocused: { table: { disable: true } },


Could we remove the disabled/selected controls on swatch group? Or define them if there is a reason to keep them.

rise-erpelding · 2025-04-28T16:22:46Z

tokens/custom/light-vars.css

 	--spectrum-swatch-border-color: rgb(0 0 0 / 51%);
-	--spectrum-swatch-border-color-light: rgb(0 0 0 / 20%);
+	--spectrum-swatch-border-color-light: rgb(0 0 0 / 42%);


Oh, is this where the light border token is coming from?

Also, do we still need --spectrum-swatch-border-color? Looks like it's now defined in tokens.

rise-erpelding · 2025-04-28T16:29:31Z

tokens/custom/light-vars.css

+	/**
+	 * `--spectrum-swatch-group-border-color` / `--spectrum-swatch-group-border-opacity`
+	 */
+	--spectrum-swatchgroup-border-color: rgb(255 255 255 / 20%);


It also looks like there's a swatch-group-border-color token that would be potentially available (but I didn't see swatch-group-border-opacity, would it be preferable to use the existing swatch-group-border-color-token and define a custom opacity token instead?

rise-erpelding · 2025-04-28T16:46:42Z

components/swatch/stories/swatch.test.js

+			testHeading: "Add",
+			isAddSwatch: true,


This coverage looks great!

One thing I noticed since I looked at both forced-colors and WHCM this time around is that we don't have a lot of contrast between the swatch and the icon (.spectrum-Swatch-icon), while I think we can make improvements to high contrast when we have a more defined spec for it, it would be nice to at least ensure that the contrast is decent for now on these icon swatches.

Here is (I think) forced colors above and WHCM below, you can see that the mixed value and add variants make it really difficult to see the icon here:

…+ story updates

…s for add swatch

…partial rounding

…lt; add missing isAddSwatch arg for swatchgroup story

…mpact

… testing grid

Co-authored-by: [ Cassondra ] <[email protected]>

cdransf added wip This is a work in progress, don't judge. skip_vrt Add to a PR to skip running VRT (but still pass the action) labels Apr 17, 2025

cdransf self-assigned this Apr 17, 2025

cdransf force-pushed the cdransf/s2-swatch-group-migration branch from ffa2cad to 37bccbb Compare April 17, 2025 23:28

adobe deleted a comment from github-actions bot Apr 17, 2025

cdransf force-pushed the cdransf/s2-swatch-group-migration branch 3 times, most recently from 91c31d2 to d0944eb Compare April 21, 2025 15:28

cdransf marked this pull request as ready for review April 21, 2025 17:51

cdransf added size-3 M ~18-30hrs; moderate effort or complexity, several work days needed. ready-for-review and removed wip This is a work in progress, don't judge. labels Apr 21, 2025

cdransf requested review from castastrophe, marissahuysentruyt, aramos-adobe and 5t3ph April 21, 2025 17:52

cdransf force-pushed the cdransf/s2-swatch-group-migration branch from 9ca18cb to f3f8289 Compare April 22, 2025 13:37

cdransf added the wip This is a work in progress, don't judge. label Apr 22, 2025

cdransf force-pushed the cdransf/s2-swatch-group-migration branch 2 times, most recently from 02c2cca to 044c357 Compare April 22, 2025 17:23

cdransf added size-8 XL ~18-54hrs; huge effort, high complexity, takes a whole sprint, maybe break down. and removed wip This is a work in progress, don't judge. size-3 M ~18-30hrs; moderate effort or complexity, several work days needed. labels Apr 22, 2025

rise-erpelding requested changes Apr 24, 2025

View reviewed changes

cdransf force-pushed the cdransf/s2-swatch-group-migration branch from 0fcbcb5 to db0370d Compare April 24, 2025 15:30

castastrophe requested changes Apr 24, 2025

View reviewed changes

cdransf force-pushed the cdransf/s2-swatch-group-migration branch from 8adbddb to f585079 Compare April 24, 2025 19:37

cdransf force-pushed the cdransf/s2-swatch-group-migration branch from 0887905 to d44dbf8 Compare April 24, 2025 19:51

cdransf requested review from castastrophe and rise-erpelding April 24, 2025 19:51

cdransf force-pushed the cdransf/s2-swatch-group-migration branch from d44dbf8 to f4b2157 Compare April 28, 2025 15:23

rise-erpelding requested changes Apr 28, 2025

View reviewed changes

cdransf and others added 23 commits April 28, 2025 17:20

feat(swatch+swatchgroup): S2 migration

dd8673b

chore(swatch+swatchgroup): update tokens and mods

2b661a3

chore(swatch+swatchgroup): support interactive states for add swatch …

74bb7d5

…+ story updates

chore(swatch+swatchgroup): add hovered hover + keyboard focus control…

9ceb4cb

…s for add swatch

chore(swatch+swatchgroup): add hovered hover + keyboard focus control…

0250f10

…s for add swatch

chore(swatch+swatchgroup): add focus ring

2b41e9b

chore(swatch+swatchgroup): spacing token updates and refactoring

4cb1812

chore(swatch+swatchgroup): update custom vars to use opacity token

ced203d

fix(swatch+swatchgroup): duplicate custom properties

f555cae

chore(swatch+swatchgroup): update changelog

8f9bfc2

chore(swatch+swatchgroup): update corner rounding

d4b142e

fix(swatch+swatchgroup): style fix

e2f2fb3

fix(swatch+swatchgroup): no rounding is default; replace test case w/…

e049a15

…partial rounding

chore(swatch+swatchgroup): support swatchgroup border

1edfc49

chore(swatch+swatchgroup): swap none to partial rounding as the defau…

1ade02b

…lt; add missing isAddSwatch arg for swatchgroup story

chore(swatch+swatchgroup): add mediumLarge density variant; remove co…

1da83a9

…mpact

chore(swatch+swatchgroup): story, control and test cleanup

b1f6cb1

chore(swatch+swatchgroup): add hover + active states to add variation…

24402a2

… testing grid

fix(swatch+swatchgroup): update border color

9def3d7

fix(swatch+swatchgroup): changelog + mod removal

cd8e6c5

Update components/swatchgroup/index.css

e13dbc4

Co-authored-by: [ Cassondra ] <[email protected]>

fix(swatch+swatchgroup): split medium + large sizing back out

f239818

fix(swatch+swatchgroup): deduplicate controls inherited from swatch

bc1dfdb

cdransf force-pushed the cdransf/s2-swatch-group-migration branch from f4b2157 to bc1dfdb Compare April 29, 2025 00:20

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(swatch+swatchgroup): S2 migration #3677

feat(swatch+swatchgroup): S2 migration #3677

cdransf commented Apr 17, 2025 •

edited

Loading

changeset-bot bot commented Apr 17, 2025 •

edited

Loading

github-actions bot commented Apr 17, 2025 •

edited

Loading

github-actions bot commented Apr 17, 2025 •

edited

Loading

swatch

swatchgroup

tokens

rise-erpelding left a comment

rise-erpelding Apr 24, 2025

cdransf Apr 24, 2025

rise-erpelding Apr 24, 2025

cdransf Apr 24, 2025

rise-erpelding Apr 24, 2025

cdransf Apr 24, 2025

rise-erpelding Apr 28, 2025

rise-erpelding Apr 24, 2025

cdransf Apr 24, 2025 •

edited

Loading

castastrophe Apr 24, 2025

castastrophe left a comment

castastrophe Apr 24, 2025

castastrophe Apr 24, 2025

cdransf Apr 24, 2025

rise-erpelding Apr 28, 2025

rise-erpelding left a comment

rise-erpelding Apr 28, 2025

rise-erpelding Apr 28, 2025

rise-erpelding Apr 28, 2025

rise-erpelding Apr 28, 2025

marissahuysentruyt Apr 28, 2025

rise-erpelding Apr 28, 2025

rise-erpelding Apr 28, 2025

rise-erpelding Apr 28, 2025

rise-erpelding Apr 28, 2025

feat(swatch+swatchgroup): S2 migration #3677

Are you sure you want to change the base?

feat(swatch+swatchgroup): S2 migration #3677

Conversation

cdransf commented Apr 17, 2025 • edited Loading

Description

Removed custom properties

New custom properties

New mods

How and where has this been tested?

Validation steps

Regression testing

Screenshots

To-do list

changeset-bot bot commented Apr 17, 2025 • edited Loading

🦋 Changeset detected

github-actions bot commented Apr 17, 2025 • edited Loading

github-actions bot commented Apr 17, 2025 • edited Loading

File metrics

Summary

swatch

swatchgroup

tokens

rise-erpelding left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

cdransf Apr 24, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

castastrophe left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rise-erpelding left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

cdransf commented Apr 17, 2025 •

edited

Loading

changeset-bot bot commented Apr 17, 2025 •

edited

Loading

github-actions bot commented Apr 17, 2025 •

edited

Loading

github-actions bot commented Apr 17, 2025 •

edited

Loading

cdransf Apr 24, 2025 •

edited

Loading