Skip to content

ci(release): publish via Trusted Publisher workflow and streamline CI - #527

Merged
microshine merged 2 commits into
masterfrom
codex/trusted-publisher-release
Aug 14, 2026
Merged

ci(release): publish via Trusted Publisher workflow and streamline CI#527
microshine merged 2 commits into
masterfrom
codex/trusted-publisher-release

Conversation

@microshine

Copy link
Copy Markdown
Contributor

Summary

Replaces the npm token-based publishing in the CI with a Trusted Publisher workflow and streamlines the release process.

Changes

  • .github/workflows/release.yml (new): Adds a dedicated, manually triggered (workflow_dispatch) release workflow that:
    • Prepares a release (bumps version, builds, packs the tarball, generates a release summary with changes since the previous tag).
    • Publishes the prepared package to npm via Trusted Publisher (using id-token: write and an npm environment), removing the need for long-lived npm tokens.
    • Commits the release version, creates and pushes the vX.Y.Z tag plus the major vX tag, and creates a GitHub Release with auto-generated notes.
  • .github/workflows/library.yml: Removes the publish job (now handled by the new release workflow).
  • package.json: Updates the repository URL to use HTTPS.

Notes

  • Requires an OpenID Connect (Trusted Publisher) trust relationship to be configured for the npm environment on the npmjs publisher before first use.

- Add a new release workflow that uses Trusted Publisher for npm publishing
- Remove the publish job from the library CI workflow
- Update the repository URL to use HTTPS
@microshine
microshine requested a review from donskov August 4, 2026 12:05
@microshine microshine self-assigned this Aug 4, 2026
@coveralls

coveralls commented Aug 4, 2026

Copy link
Copy Markdown

Coverage Status

coverage: 72.274%. remained the same — codex/trusted-publisher-release into master

@microshine
microshine merged commit 1612ea6 into master Aug 14, 2026
7 checks passed
@microshine
microshine deleted the codex/trusted-publisher-release branch August 14, 2026 08:30
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.

3 participants