Repository navigation
👷 ci: release workflow with npm trusted publishing - #7
Merged
Merged
Conversation
Changesets versions the package and release.yml publishes it with pnpm over OIDC, the pipeline of fragiola/dockable for a single package. `pnpm check:package` packs the package, checks the tarball (files, publint, attw) and smoke-tests it from a scratch project; CI runs it, and the release's pack job runs it on the tarball it publishes. CI's Changesets job asks for a changeset on every PR that changes what ships. The first changeset releases 0.1.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 17, 2026
Merged
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
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
Publishing for the
fragiolapackage, the same pipeline as fragiola/dockable for a single package:main,.github/workflows/release.ymleither opens/updates the Version Packages PR, or (once it is merged) packs the package, checks that tarball and publishes it with pnpm over npm trusted publishing (OIDC, with provenance, no npm token), then pushes thefragiola@<version>tag and creates the GitHub release. Actions are pinned by commit, as in Dockable.pnpm check:package(scripts/check-package.ts): packs with pnpm, checks the tarball ships onlydist/+ manifest files and everybin/exportstarget, runs publint (strict) and attw (esm-only), then installs it with npm in a scratch project and runsfragiola --version, both exports and an MCPinitialize+tools/listover stdio. The release's pack job runs it on the very tarball it publishes (--tarballs).mainruns the release..changeset/first-release.mdreleases 0.1.0.docs/releasing.md: the maintainer's first steps and the later-release / failure runbook. AGENTS.md and README updated.Before merging
Merging this PR starts the release (it opens the Version Packages PR). Do steps 1–4 of
docs/releasing.mdfirst: the workflow permission to open PRs, thenpmenvironment (main only), the0.0.0stub published by hand with pnpm, andnpm trust github fragiola --file release.yml --repo fragiola/cli --environment npm --allow-publish.Notes
.changeset/*.mdandCHANGELOG.mdare excluded from Biome.--ignore-scripts(Dockable filters{.}): the dependencies are present next to the OIDC token but never run.Validation
pnpm check,pnpm typecheck,pnpm test(96 passed, 5 new for the check's helpers),pnpm check:package(✓ fragiola@0.0.0 can be published),pnpm changeset status --since=origin/main(fragiola → 0.1.0).🤖 Generated with Claude Code