My GitHub Action is not publishing my package to npm

[sebastianjnuwu]

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/"

[sebastianjnuwu]

https://github.com/sebastianjnuwu/nlogin/actions/runs/7365251588/job/20046390721

[sebastianjnuwu]

nlogin-js@1.0.3 publish skipped.

[mcous]

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

Run JS-DevTools/npm-publish@v3
  with:
    token: ***
📦 nlogin-js@1.0.3
=== Contents ===
117 B	.github/FUNDING.yml
387 B	.github/renovate.json
500 B	.github/workflows/npm-publish.yml
1.4 kB	.github/workflows/release.yml
10.3 kB	LICENSE
2.8 kB	README.md
4.8 kB	lib/hash.js
4.1 kB	lib/login.js
908 B	package.json

On subsequent runs of the action, the publish was skipped because version 1.0.3 already existed in the registry

[sebastianjnuwu]

But the GitHub action didn't work, as it wasn't working I deleted the action and sent it via command line

[mcous]

But the GitHub action didn't work

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.)

I deleted the action and sent it via command line

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.

[sebastianjnuwu]

It actually published 1.0.3, when I published it via the cli it was 2.0.0, how strange that '1.0.3' wasn't listed before it was just 1.0.2 > 2.0.0. I think it was npm cache or something!

[sebastianjnuwu]

Thanks for your help 🐾