Skip to content

ci(embed): publish @turbodocx/embed to npm on embed-v* releases - #89

Merged
nicolasiscoding merged 1 commit into
mainfrom
ci/publish-embed
Oct 7, 2026
Merged

nicolasiscoding merged 1 commit into
mainfrom
ci/publish-embed

Conversation

@nicolasiscoding

Copy link
Copy Markdown
Member

What

Adds .github/workflows/publish-embed.yml. On a GitHub Release tagged embed-v* it builds and tests packages/embed, then runs npm publish --workspace packages/embed --access public --provenance with NPM_TOKEN. It mirrors publish-js.yml.

Why

@turbodocx/embed (added in #77) had no publish workflow, so the v0.8.0 lockstep release skipped it. It has never been published to npm (npm view @turbodocx/embed returns 404). Integrators currently need a vendored tarball.

Verified locally

  • npm run build -w packages/embed: OK
  • npm test -w packages/embed: 3 suites, 54 tests passing
  • npm pack --dry-run -w packages/embed: @turbodocx/embed@0.2.0, 15 files

After merge

Cut embed-v0.2.0 (gh release create embed-v0.2.0 --target <merge sha>). This is the first publish of a new package under @turbodocx, so NPM_TOKEN must be allowed to create packages in the scope: a classic automation token, or a granular token with the @turbodocx scope or all packages.

Related: #88 (publish workflows run on every release tag).

🤖 Generated with Claude Code

https://claude.ai/code/session_01FPrhr7EjqkqyWBLagUXqDf

@turbodocx/embed had no publish workflow, so it was skipped by the SDK
release and has never reached npm. Mirror publish-js.yml: on a release
tagged embed-v*, build and test the workspace, then npm publish with
provenance using NPM_TOKEN.
@nicolasiscoding
nicolasiscoding merged commit 707f725 into main Oct 7, 2026
13 checks passed
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