Repository navigation
build(release): publish the package from a release workflow - #190
Closed
erkamyaman wants to merge 1 commit into
Closed
erkamyaman wants to merge 1 commit into
erkamyaman wants to merge 1 commit into
Conversation
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Comment |
|
View your CI Pipeline Execution ↗ for commit 1555489
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
This was referenced Oct 3, 2026
Closed
erkamyaman
marked this pull request as ready for review
October 3, 2026 13:47
erkamyaman
marked this pull request as draft
October 3, 2026 13:51
Adds a Release workflow run by hand on main. It runs the CI checks, sets the version, takes the notes from the changelog, checks the packed tarball through a local registry, publishes with provenance through npm trusted publishing, then commits the version, tags it and creates the GitHub release. The publishing guide covers the one-time npm setup and keeps the manual commands as a fallback.
erkamyaman
force-pushed
the
ci/release-workflow
branch
from
October 7, 2026 20:44
1555489 to
c30241f
Compare
22 tasks done
erkamyaman
added a commit
that referenced
this pull request
Nov 7, 2026
Adds the Release workflow from #190: run by hand on main, it runs CI on the commit, checks the changelog section, packs and verifies the tarball, publishes with provenance through npm trusted publishing, then tags and creates the GitHub release. publishing.md covers the one-time setup and keeps the manual commands as a fallback.
Member
Author
|
Folded into the 1.0.0 release PR, #460 (commit 33d5ee0). The workflow is unchanged. Generated by Claude Code |
erkamyaman
added a commit
that referenced
this pull request
Nov 7, 2026
Sets the package to 1.0.0 and turns the changelog's Unreleased section into 1.0.0. The vite peer range is >=6, the mobile entry points stay through 1.x, and any loopback port passing the origin check is documented. Adds the Release workflow from #190: run by hand on main, it runs CI, checks the changelog, verifies the tarball, publishes with provenance through npm trusted publishing, tags the published commit and creates the GitHub release.
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.
Adds a Release workflow (
.github/workflows/release.yml) so the package is published from GitHub Actions instead of by hand.What it does
Run by hand from the Actions tab, on
mainonly, with a version (patch,minoror an exactx.y.z):ci.ymlas a reusable workflow).packages/devtools/package.json.## <version>section ofpackages/devtools/CHANGELOG.md, and stops if there isn't one.pnpm verify:publish --tarball=....--provenancethrough npm trusted publishing (OIDC, no token stored). It skips the publish if that version is already on npm, so a rerun finishes a half-done release.devtools@<version>and creates the GitHub release.publishing.mdcovers the one-time setup and each release, and keeps the manual commands as a fallback.Setup needed before the first run
@pangular-inspector/devtoolssettings, add a trusted publisher: GitHub Actions, ownerpangular-inspector, repositorydevtools, workflowrelease.yml, no environment.mainis protected, let GitHub Actions push the version commit and tag.Checks
actionlintandpnpm format:checkpass0.0.7vs0.0.70pnpm verify:publish --tarball=...passed locally