Repository navigation
👷 Use staged publishing #41
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| name: Publish | ||
| name: Stage | ||
|
|
||
| on: | ||
| push: | ||
|
|
@@ -30,11 +30,14 @@ jobs: | |
| with: | ||
| node-version: 24 | ||
|
|
||
| - name: Setup npm with staged publishing | ||
| run: npm install --global npm@11.21.0 | ||
|
|
||
| - name: Build NPM | ||
| run: deno task build:npm ${{steps.vars.outputs.version}} | ||
|
|
||
| - name: dry run publish | ||
| run: npm publish --dry-run --access=public --tag=verify | ||
| - name: dry run staged publish | ||
| run: npm stage publish --dry-run --access=public --tag=verify | ||
| working-directory: ./build/npm | ||
|
|
||
| - name: upload build | ||
|
|
@@ -43,7 +46,7 @@ jobs: | |
| name: npm-build | ||
| path: ./build/npm | ||
|
|
||
| publish-npm: | ||
| stage-npm: | ||
| needs: verify-npm | ||
| runs-on: ubuntu-latest | ||
|
|
||
|
|
@@ -53,12 +56,15 @@ jobs: | |
| with: | ||
| node-version: 24 | ||
|
|
||
| - name: Setup npm with staged publishing | ||
| run: npm install --global npm@11.21.0 | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. lol. great minds @jbolda, great minds..... I also thought that was weird to have to burn a step just configuring npm, but it turns out that the answer is "ignore community requests" 🤷🏻♂️
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also, upgrading to the default Node26 container gets you |
||
|
|
||
| - name: download build | ||
| uses: actions/download-artifact@v4 | ||
| with: | ||
| name: npm-build | ||
| path: ./build/npm | ||
|
|
||
| - name: Publish NPM | ||
| run: npm publish --access=public --tag=latest | ||
| - name: Stage NPM publish | ||
| run: npm stage publish --access=public --tag=latest | ||
| working-directory: ./build/npm | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, does
--dry-runwork on staged?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, I was wondering the same thing, so I ran it locally :)