Uh oh!
There was an error while loading. Please reload this page.
release: @directededges/specs-schema v0.21.0 + @directededges/specs-cli v0.16.0 - #109
Merged
Conversation
* docs(adr): draft ADR-051 platform code-syntax token profiles Add FIGMA_SYNTAX_WEB/IOS/ANDROID profiles to format.tokens (DRAFT). Refs #103 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(adr): claim ADR-051 in INDEX Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * feat(schema): implement ADR-051 platform code-syntax token profiles Add FIGMA_SYNTAX_WEB/IOS/ANDROID to format.tokens (Config + ResolvedConfig) and component.schema.json. Default unchanged (TOKEN); empty platform syntax falls back to TOKEN output (transformer behavior). Folds into unreleased 0.21.0. Update Config.test-d.ts, docs, and CHANGELOG. Refs #103 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(adr): mark ADR-051 ACCEPTED; move INDEX row to Accepted Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
* feat(cli): accept FIGMA_SYNTAX_* token profiles (ADR 051) Implement the CLI side of ADR 051, which adds three additive `format.tokens` serialization profiles: FIGMA_SYNTAX_WEB, FIGMA_SYNTAX_IOS, and FIGMA_SYNTAX_ANDROID. - ConfigLoader: add the three values to the validTokens allow-list so they are no longer reset to the TOKEN default during validation. - ConfigTemplates: list the new values in the init scaffold comment. - Tests: cover all eight valid token values plus lowercase normalization for FIGMA_SYNTAX_IOS. - Docs: document the platform code-syntax profiles in the token format guide (profile section, comparison table, when-to-use list). The schema package and config/commands doc sections already carried the new enum; generate passes the resolved config through unchanged and applyCustomTokens is unaffected. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(cli): changelog entry for FIGMA_SYNTAX_* token profiles (ADR-051) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
nathanacurtishad a problem deploying
to
npm-publish
May 22, 2026 18:01 — with 
GitHub Actions
Failure
nathanacurtishad a problem deploying
to
npm-publish
May 22, 2026 18:01 — with GitHub Actions
Failure
CI publish (release-cli.yml) checks out the tag and runs `npm ci` + build + test using only the specs repo. Two things prevented that: - Root package.json linked specs-from-figma via `file:../specs-from-figma`, so the committed lockfile resolved it to a sibling path absent in CI (ERR_MODULE_NOT_FOUND). Swap to versioned `^0.19.0` and regenerate the lockfile so it resolves from the npm registry. - specs-schema is a workspace member whose dist/ is gitignored, and the CLI imports runtime values from it. Add a "Build schema" step before the CLI build/test so module resolution succeeds. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
nathanacurtishad a problem deploying
to
npm-publish
May 22, 2026 18:11 — with GitHub Actions
Failure
nathanacurtishad a problem deploying
to
npm-publish
May 22, 2026 18:14 — with GitHub Actions
Failure
…ing is used setup-node's registry-url writes an .npmrc _authToken line and exports a placeholder NODE_AUTH_TOKEN, forcing token auth (404). Removing it lets npm use OIDC trusted publishing. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
nathanacurtishad a problem deploying
to
npm-publish
May 22, 2026 18:16 — with GitHub Actions
Failure
nathanacurtis
marked this pull request as ready for review
May 22, 2026 18:23
…-cli-0.16.0 # Conflicts: # adr/INDEX.md
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 freeto 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.
Summary
Config.format.tokensplatform code-syntax profiles (FIGMA_SYNTAX_WEB/IOS/ANDROID).release-cli.ymlbuildable from a clean checkout (root dep versioned, lockfile regenerated, schema built before tests).Both packages published to npm. See
packages/schema/CHANGELOG.mdandpackages/cli/CHANGELOG.md.Closes#103