Version Packages - #1436
Merged
Merged
Conversation
Contributor
🎨 Token Changes ReportTokens Changed (0)Original Branch: This comment was automatically generated by the token diff tool. 🤖 |
Contributor
🧩 Component Schema Changes ReportNo component schema changes detected.This comment was automatically generated by the component schema diff tool. 🤖 |
Contributor
Run report for f1aad98dTotal time: 5m 10s | Comparison time: 9m 42s | Estimated savings: 4m 32s (46.7% faster)
Expanded report
Changed files |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 9, 2026 22:15
2b4aa5b to
f1aad98
Compare
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@adobe/spectrum-design-data@3.1.0
Minor Changes
905bc1dThanks @GarthDB! - Route opacity tokens to the.Color themecollection in the Figma variablesexporter and diff (they were misrouted to
.Platform scaledespite being aFLOAT), and resolve
S2.Color-theme's bare-named alias variables throughtheir
.Color themetargets instead of reporting themfigma-only(closes DNA-1953).
.Color theme(colorTheme/*) in both the alias-target pre-pass and the flat-tokendispatch;
process_color_set_token's FLOAT/COLOR type inference now checksall
setsmembers instead of only the first.diff_valuesnow falls back toresolve_alias_targetfor bare (slash-less) Figma names, recovering all 35S2.Color-themeopacity variables as matches.@adobe/design-data-wasm@0.9.0
Minor Changes
47db5e9Thanks @GarthDB! - Route$ref-backed color-set CTR tokens (e.g.action-bar-border-color,popover-border-color,card-selection-background-color) through the Figmavariables diff's per-mode comparison instead of reporting them
skipped-uncovered(closes spectrum-design-data-2god).diff_values's multi-mode routing gatenow also accepts a variable whose design-data token is CTR/relationship-backed
(
graph.has_relationship_record), not only one carrying aconceptId/setUuiddirectly on its resolved record — the link a
$ref-backed color-set CTR carriesonly on its
RelationshipRecord, never on the resolvedTokenRecord.@adobe/spectrum-component-api-schemas@6.1.54
Patch Changes
905bc1d]:@adobe/design-system-registry@5.0.36
Patch Changes
905bc1d]:@adobe/design-data@3.0.9
Patch Changes
47db5e9]:@adobe/design-data-agent-mcp@1.9.9
Patch Changes
47db5e9,905bc1d]:@adobe/design-data-mcp@1.7.39
Patch Changes
47db5e9,905bc1d]:@adobe/spectrum-design-data-mcp@1.1.70
Patch Changes
@adobe/design-data-tui@0.13.0
Minor Changes
47db5e9Thanks @GarthDB! - Route$ref-backed color-set CTR tokens (e.g.action-bar-border-color,popover-border-color,card-selection-background-color) through the Figmavariables diff's per-mode comparison instead of reporting them
skipped-uncovered(closes spectrum-design-data-2god).diff_values's multi-mode routing gatenow also accepts a variable whose design-data token is CTR/relationship-backed
(
graph.has_relationship_record), not only one carrying aconceptId/setUuiddirectly on its resolved record — the link a
$ref-backed color-set CTR carriesonly on its
RelationshipRecord, never on the resolvedTokenRecord.s2-tokens-viewer@0.2.20
Patch Changes
47db5e9]:component-options-editor@1.1.55
Patch Changes
markdown-generator@0.1.72
Patch Changes
905bc1d]:@adobe/token-corpus-migrate@0.1.42
Patch Changes
905bc1d]:@adobe/token-naming-audit@0.1.52
Patch Changes
47db5e9,905bc1d]: