build(release): publish the package from a release workflow - #190
Draft
erkamyaman wants to merge 2 commits into
Draft
erkamyaman wants to merge 2 commits into
erkamyaman wants to merge 2 commits into
Conversation
…wners Adds skills for fixing one issue, working through a batch and settling open decisions, a glossary of project terms, and a repository section in AGENTS.md with its commands and the rules that fail quietly. CLAUDE.md now imports AGENTS.md, and the generic Angular rules move to .claude/rules. Adds a publish check against a local registry, a weekly run of it on the newest versions our ranges allow, issue triage from the issue forms, an area prefix for issue titles, a shared setup action for the workflows, and both maintainers as code owners. Refs santoshyadavdev#100
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.
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 |
github-actions
Bot
added
area: docs
|
View your CI Pipeline Execution ↗ for commit 470a49a
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
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
1 participant
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/ng-devtools/package.json.## <version> - <date>section ofpackages/ng-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.ng-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
@santoshyadavdev/ng-devtoolssettings, add a trusted publisher: GitHub Actions, ownersantoshyadavdev, repositoryangular-devtools, workflowrelease.yml, no environment.mainis protected, let GitHub Actions push the version commit and tag.Checks
actionlintandpnpm format:checkpass0.0.6vs0.0.60pnpm verify:publish --tarball=...passed locally