ci(embed): CI + Changesets + OIDC trusted-publish pipeline (ENG-8647) - #3
Merged
Conversation
…647) - .changeset/config.json (access: public, updateInternalDependencies: patch, baseBranch: main) + README - .github/workflows/ci.yml: pull_request + push to main -> install, lint, format:check, typecheck, test, build (no publish perms) - .github/workflows/release.yml: push to main -> changesets/action with id-token: write for OIDC trusted publishing + npm provenance; upgrades npm to >= 11.5; no long-lived NPM_TOKEN Note: the very first 0.1.0 publish is bootstrapped manually (ENG-8648) so the npmjs.com trusted publisher can be attached; changesets drives 0.1.1+ after. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
andrewc-monad
force-pushed
the
feature/eng-8647
branch
from
June 17, 2026 16:50
be9a69b to
384bb43
Compare
…rap) Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
andrewc-monad
requested review from
brenth-monad
and removed request for
mattj-monad
June 17, 2026 16:55
brenth-monad
approved these changes
Jun 18, 2026
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
2 participants
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.
What
Adds the build/test CI and the npm release pipeline. Stacked on #2 (ENG-8646) — review/merge #1 → #2 → this in order.
.changeset/config.json—access: public,updateInternalDependencies: patch,baseBranch: main. Drives versioning once the repo goes multi-package (form-core depends on connect later)..github/workflows/ci.yml(PRs + push to main): install → lint → format:check → typecheck → test → build. No publish permissions. (Deliberately does not gate onchangeset status, so PRs aren't blocked by missing changesets.).github/workflows/release.yml(push to main):changesets/action@v1withid-token: writefor OIDC trusted publishing + npm provenance, upgrades npm to ≥ 11.5, no long-livedNPM_TOKEN.Bootstrap caveat (handled in ENG-8648)
The first
0.1.0publish is done manually so the npmjs.com trusted publisher can be attached to the (not-yet-existent) package. After that, Changesets drives0.1.1+fully tokenless. Until the trusted publisher is configured, the release job's publish step will no-op/fail on auth — non-destructive.Verification
🤖 Generated with Claude Code