name: Publish to npm # Publishes the package to npm whenever a GitHub Release is published. # # The release tag (e.g. v1.2.3) is the source of truth for the version: # package.json is set from the tag, the package is published, and the # version bump is committed back to master. You do not edit package.json # by hand for a release - just publish a GitHub Release with the right tag. # # Authentication uses npm Trusted Publishing (OIDC) - no token or secret is # needed. Configure a trusted publisher for this package on npmjs.com: # Repository: Skylar-Tech/node-red-contrib-matrix-chat # Workflow: publish.yml on: release: types: [published] jobs: publish: runs-on: ubuntu-latest permissions: contents: write # commit the version bump back to master id-token: write # npm Trusted Publishing (OIDC) + provenance steps: - name: Checkout master uses: actions/checkout@v4 with: ref: master - name: Set up Node.js uses: actions/setup-node@v4 with: node-version: 22 registry-url: https://registry.npmjs.org - name: Update npm # Trusted Publishing requires npm 11.5.1 or newer; Node 22 ships npm 10. run: npm install -g npm@latest - name: Set version from release tag run: npm version "${GITHUB_REF_NAME#v}" --no-git-tag-version --allow-same-version - name: Publish to npm run: npm publish --provenance --access public - name: Commit version bump back to master run: | if git diff --quiet; then echo "package.json already at ${GITHUB_REF_NAME#v}; nothing to commit." exit 0 fi git config user.name "github-actions[bot]" git config user.email "41898282+github-actions[bot]@users.noreply.github.com" git commit -am "Set version to ${GITHUB_REF_NAME#v}" git push origin HEAD:master \ || echo "::warning::Could not push the version bump to master (branch protection?). The package was still published."