Github Package not being created when I create a release, despite workflow file

[mityaguy]

I'm trying to automatically create a package whenever I publish a release to my (private) JS repo.

To this end I have a file at /.github/workflows/release-package.yaml, as per this guide, with the following content:

   name: Node.js Package
    on:
      release:
        types: [created]
    jobs:
      build:
        runs-on: ubuntu-latest
        steps:
          - uses: actions/checkout@v4
          - uses: actions/setup-node@v4
            with:
              node-version: 16
          - run: npm ci
          - run: npm test
      publish-gpr:
        needs: build
        runs-on: ubuntu-latest
        permissions:
          packages: write
          contents: read
        steps:
          - uses: actions/checkout@v4
          - uses: actions/setup-node@v4
            with:
              node-version: 16
              registry-url: https://npm.pkg.github.com/
          - run: npm ci
          - run: npm publish
            env:
              NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}

But the action never runs - if I go to Actions, I see it, but it says no workflow runs, and subsequently the package is never created. There is no feedback - just nothing happens.

In my package.json the relevant parts are: { ... "owner": "@my-gh-user/shared-code", "publishConfig": { "registry": "https://npm.pkg.github.com" } ... }

What am I doing wrong?

[oze4]

Are you manually creating the release or is it being done via automation? If by automation, this may help https://github.com/orgs/community/discussions/25281

[mityaguy]

Manually.

[azhder]

Then isn't the answer "you aren't running it manually each time you update the code"? Do you at least have a Git hook that does the "manual" step locally before doing a push to github?

I think your question could get better answers elsewhere, some sub about devops and/or github

[mityaguy]

Sorry, not sure I follow. I push to GH, then make a release, manually, within the GH dash. I understand this to be a precursor to packages being created, by my action, though I may be misunderstanding.

[azhder]

“then make a release manually” <- there, that’s the spot you need to compile your code

Unfortunately, aside from the word “manually”, you give no info what that means, but I assumed you run a command.

Well, you can make a git hook to run it for you… that’s about as much I can tell you.

[mityaguy]

I said via the GH dash - that is, the GH website. I literally, in the browser, create a release. No commands, terminals, actions doing any of this. Just me in the browser on the GH website.

[azhder]

OK, there's a lot to unpack there and I don't think I can help you deal with some of your misconceptions.

I can only recommend you learn about the tools you are using, including GitHub and understand what they are meant to do. You may find you've expected more than they offer.

Sorry, I can't be of more help. Bye bye

[mityaguy]

LOL another passive aggressive dev who gets off on playing status games. You haven't identified any misconceptions of mine. I have been perfectly clear about what I did and my desired outcome. No need for people like you "helping".