Skip to content

Use staged npm publishing for language releases - #7

Merged
konojunya merged 1 commit into
mainfrom
jj/staged-language-publishing
Sep 3, 2026
Merged

Use staged npm publishing for language releases#7
konojunya merged 1 commit into
mainfrom
jj/staged-language-publishing

Conversation

@konojunya

Copy link
Copy Markdown
Member

背景

Language package releases should use the same human-approved npm supply-chain boundary as the engine package. The first release remains a one-time authenticated bootstrap because npm requires an existing package before Trusted Publisher configuration.

実装方法

  • pin npm 11.15.0 and replace direct publishing with npm stage publish
  • add the first-release bootstrap and subsequent stage, inspect, 2FA approve, and verify flow
  • retain exact language-v<version> tag, ancestry, tests, types, package audit, registry, and provenance gates

テスト方法

  • npm ci
  • npm run test:language
  • npm run typecheck:language
  • npm run pack:check
  • all existing schema and conformance validation commands
  • npm audit --audit-level=high
  • parse all workflow YAML files

Review 視点 / 懸念点

  • The future Trusted Publisher must allow npm stage publish for workflow release-language.yaml.
  • The initial 0.1.0 package is published manually before this trust relationship can be configured.

@konojunya
konojunya merged commit 98865b2 into main Sep 3, 2026
2 checks passed
@konojunya
konojunya deleted the jj/staged-language-publishing branch September 3, 2026 12:38
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.

1 participant