docs: update TOKENS_STUDIO.md release pipeline (css-bundle + exports-map) - #5278
Merged
Merged
Conversation
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.
Updates § The release pipeline in
documentation/agent-instructions/TOKENS_STUDIO.md, which was stale after recent merges:generate:css-bundlestep producing the committedsrc/tokens/css/variables.cssbundle (feat: add bundled variables.css to the Tokens Studio release pipeline #5209), including that it also widens the semantic layer viascripts/widen-semantic-scope.mjs(Emit the semantic token layer under the [data-color-scheme] scopes #5226).exportsmap" claim —publish_tokens.yamlinjects./next/css/*,./next/dtcg/*and./next/ts/*on every beta publish (ADR 0009, ci: set up automatic beta releases for eds-tokens #5180), and Storybook loads the beta bundle (chore: load the eds-tokens beta bundle in storybook for the /next migration #5224).3.0.0-beta.Nviapublish_tokens.yaml) with a cross-link to BETA_RELEASE_GUIDE.md.ADR-0010 is deliberately not referenced — it is still Proposed (#5199); the dangling reference in
tokens_studio_release.yamlis tracked separately in #5244.Closes #5241