Skip to content

build(release): publish to npm via Trusted Publishing (OIDC) with semantic-release 25 #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SahinurDEV wants to merge 1 commit into
base: main
Choose a base branch
from
Open

build(release): publish to npm via Trusted Publishing (OIDC) with semantic-release 25 #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -318,7 +318,7 @@ npm publish --access public

`scripts/publish.sh` wraps that sequence with a confirmation prompt, and `RELEASE_NOTES.md` has a ready-to-paste description for the GitHub Release / npm announcement.

For every release after the first, `.github/workflows/release.yml` runs [semantic-release](https://semantic-release.gitbook.io/) on pushes to `main` — it derives the next version from [Conventional Commits](https://www.conventionalcommits.org/), updates `CHANGELOG.md`, tags, and publishes, but only once you add an `NPM_TOKEN` repository secret. Until then it's a no-op (see the docs site's [Contributing](https://sahinurdev.github.io/ForgeData/docs.html#contributing) section); it never requires a token to just sit there ready.
For every release after the first, `.github/workflows/release.yml` runs [semantic-release](https://semantic-release.gitbook.io/) on pushes to `main` — it derives the next version from [Conventional Commits](https://www.conventionalcommits.org/), updates `CHANGELOG.md`, tags, and publishes to npm via [Trusted Publishing](https://docs.npmjs.com/trusted-publishers) (OIDC, with provenance) — no `NPM_TOKEN` secret is needed. It requires a one-time trusted publisher for `@sahinur/forgedata` on npmjs.com (GitHub Actions, `SahinurDEV` / `ForgeData`, workflow `release.yml`); see the docs site's [Contributing](https://sahinurdev.github.io/ForgeData/docs.html#contributing) section.

## License

Expand Down
Loading
Loading