My GitHub Action is not publishing my package to npm #170
-
|
After "renovate" updated the dependency it stopped working I think it must be an error in the yml. Can anyone help me solve it? # This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
name: 🕊️ publish
on:
workflow_dispatch:
jobs:
publish:
runs-on: ubuntu-latest
permissions:
contents: read
packages: write # allow GITHUB_TOKEN to publish packages
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v3
with:
node-version: "20"
- run: npm test
- uses: JS-DevTools/npm-publish@v3
with:
token: ${{ secrets.NPM_TOKEN }}
registry: "https://registry.npmjs.org/" |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
|
https://github.com/sebastianjnuwu/nlogin/actions/runs/7365251588/job/20046390721 |
Beta Was this translation helpful? Give feedback.
-
|
[email protected] publish skipped. |
Beta Was this translation helpful? Give feedback.
-
|
Looking through your action logs, it looks like your package was successfully published by the first run of the action after the update: https://github.com/sebastianjnuwu/nlogin/actions/runs/7365196474/job/20046274967 On subsequent runs of the action, the publish was skipped because version 1.0.3 already existed in the registry |
Beta Was this translation helpful? Give feedback.
-
|
But the GitHub action didn't work, as it wasn't working I deleted the action and sent it via command line |
Beta Was this translation helpful? Give feedback.
-
I don't understand what you mean. I can see in your action logs that the action did work and published version 1.0.3 to npm at 16:36:55. (I'm in US west coast time, which is why the second screenshot shows 8:36:55 AM.) 
This action works best if you are continuously deploying from your repository's main branch. If you are not CD'ing, I recommend following GitHub's npm publish documentation and publishing your package without using any third-party action. |
Beta Was this translation helpful? Give feedback.
-
|
It actually published |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help 🐾 |
Beta Was this translation helpful? Give feedback.
Looking through your action logs, it looks like your package was successfully published by the first run of the action after the update:
https://github.com/sebastianjnuwu/nlogin/actions/runs/7365196474/job/20046274967
On subsequent runs of the action, the publish was skipped because version 1.0.3 already existed in the registry