jdeploy github action plugin not uploading to npm

[jpage4500]

sorry last question -- I tried to use the GA plugin to send to npm and it didn't seem like anything happened. I didn't see an update in npm

      - name: Build App Installer Bundles
        uses: shannah/jdeploy@master
        with:
          github_token: ${{ github.token }}
          deploy_target: npm
          npm_token: ${{ secrets.NPM_TOKEN }}

Here's my github actions script

Here's the results

[shannah]

The current github plugin is set to only deploy to npm on "tag", not on push/commit. I.e. you need to create a tag/release, and then it will run the publish step to npm.

Also, in this case, you don't need to manually update the version in your package.json as you do in your previous step, as the plugin will automatically set the version to whatever your tag name is.

The relevant step of the github action is:

    - name: Publish to npm
      if: ${{ inputs.deploy_target == 'npm' && github.ref_type == 'tag' }}
      shell: bash
      env:
        NODE_AUTH_TOKEN: ${{ inputs.npm_token }}
      run: |
        npm pkg set version="$TAG_VERSION"
        if [[ "${{ startsWith(inputs.jdeploy_version, 'git://') }}" == "true" ]]; then
          npm pkg set jdeploy.jdeployVersion='latest'
        else
          npm pkg set jdeploy.jdeployVersion='${{ inputs.jdeploy_version }}'
        fi
        npm pkg set jdeploy.commitHash="$GITHUB_SHA"
        $jdeploy_exec publish

[jpage4500]

ahh - thank you @shannah!

just thinking out loud.. if I want to automate this maybe I can have 2 github actions scripts:

1. runs on any push to [develop] branch

• builds the app
• gets the version (ie: "24.10.18-1234")
• creates and pushes a new git tag with the version

2. runs on any new tag

• uses the jdeploy GA

---

although 2 scripts means the app gets built twice so probably not ideal.. anyway, just trying to figure out a way to keep the app updated without doing any extra work :)

[shannah]

See my reply to your other thread, where I suggest using a combination of the semantic releases action and jDeploy. https://github.com/shannah/jdeploy-cn1test-3/blob/master/.github/workflows/jdeploy.yml

[jpage4500]

FWIW - I did try my idea above of having 2 GA scripts.. 1 to create a new tag and another which ran jdeploy on a new tag.

Turns out that 1 GA script can't trigger another one - link

There is a limitation of workflow: An action in a workflow run can’t trigger a new workflow run.

[shannah]

Yes i recall running into that issue on some other workflows. I did find some work arounds.

I'll tinker with the conventional commits combination as we use that type of flow in some internal projects and it works fine.