Skip to content

chore: switch to npm staged publishing #118

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
chenjiahan wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −14
Open

chore: switch to npm staged publishing #118

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
18 changes: 5 additions & 13 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
# This action will publish the package to npm and create a GitHub release.
name: Release

on:
Expand All @@ -10,8 +9,8 @@ on:
workflow_dispatch:

permissions:
contents: write
id-token: write
contents: read
id-token: write # Required for OIDC

jobs:
publish:
Expand All @@ -26,20 +25,13 @@ jobs:
with:
node-version: 24.15.0

- name: Setup Package Managers
- name: Setup Pnpm
run: |
npm install -g corepack@latest --force
corepack enable

- name: Install Dependencies
run: pnpm install
run: pnpm i

- name: Publish
uses: JS-DevTools/npm-publish@0fd2f4369c5d6bcfcde6091a7c527d810b9b5c3f # v4
with:
token: empty

- name: Create GitHub Release
uses: ncipollo/release-action@339a81892b84b4eeb0f6e744e4574d79d0d9b8dd # v1
with:
generateReleaseNotes: 'true'
run: pnpm stage publish --no-git-checks
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the GitHub release step

On v* tag pushes this job now ends after pnpm stage publish, and the previous ncipollo/release-action step plus contents: write permission were removed; I checked the release workflow/repo references and there is no other GitHub Release creation left. If staged publishing is meant to replace only the npm publish operation, tagged releases will no longer get GitHub release entries or generated notes, so keep the release step (and write permission) after the staging step.

Useful? React with 👍 / 👎.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@
"optional": true
}
},
"packageManager": "pnpm@11.2.2",
"packageManager": "pnpm@11.3.0",
"publishConfig": {
"access": "public",
"registry": "https://registry.npmjs.org/"
Expand Down