chore(deps): bump JS-DevTools/npm-publish from 1 to 3

[dependabot]

Bumps JS-DevTools/npm-publish from 1 to 3.

Release notes

Sourced from JS-DevTools/npm-publish's releases.

v3.0.0

The v3 release updates the action's runtime to Node.js v20, but otherwise, there are no public API changes.

BREAKING CHANGES

• The action will now run on Node.js v20 instead of v16

Bug fixes

• action: update runtime to Node.js v20 (#150)

v2.2.2

Bug Fixes

• use validated package.json version for comparisons (#147), closes #139

v2.2.1

Bug Fixes

• action: update semver dep, esbuild and vitest dev deps (#114)
• npm: do not assume error code is a string (#120), closes #119

v2.2.0

Features

• Allow --ignore-scripts to be disabled in order to support publish lifecycle hooks (#102)

v2.1.0

Features

• Add explicit support for --provenance (#92), closes #88

Bug Fixes

• Handle missing latest tag during version check (#90), closes #89

v2.0.0

Welcome to v2 of JS-DevTools/npm-publish! We've been doing some spring cleaning to fix all our (known) bugs and knock out some longstanding feature requests. This release has some breaking changes, so please read carefully!

BREAKING CHANGES

• The type output is now an empty string instead of none when no release occurs

  - - if: ${{ steps.publish.outputs.type != 'none' }}
  + - if: ${{ steps.publish.outputs.type }}
      run:  echo "Version changed!"

• The check-version and greater-version-only options have been removed and replaced with strategy.
  • Use strategy: all (default) to publish all versions that do not yet exist in the registry.

... (truncated)

Changelog

Sourced from JS-DevTools/npm-publish's changelog.

v1.4.0 (2020-10-02)

• Added support NPM's --tag argument, which allows packages to be published to a named tag that can then be installed using npm install <package-name>@<tag>

• Added support for NPM's --access argument, which controls whether scoped packages are publicly accessible, or restricted to members of your NPM organization

Full Changelog

v1.3.0 (2020-10-01)

• NPM-Publish can now successfully publish a brand-new package to NPM. Previously it failed because it couldn't determine the previous package version. ([PR #12](JS-DevTools/npm-publish#12) from @​ZitRos)

Full Changelog

v1.2.0 (2020-07-23)

• Added support for running NPM in "dry run" mode, which doesn't actually publish, but reports details of what would have been published.

Full Changelog

v1.1.0 (2020-03-29)

• FIX: The configured NPM registry and token are now used all NPM commands, not just for publishing. This ensures that npm-publish works with private packages and custom registries

Full Changelog

v1.0.0 (2020-01-21)

Initial release 🎉

Commits

• 19c28f1 chore(release): 3.1.1
• 1e4a74d fix: include registry URL pathname in npm config (#186)
• 79051c0 chore(release): 3.1.0
• aa4addf feat(dry-run): always print publish results in dry run (#185)
• 126874f chore(deps): bump the production group with 2 updates (#180)
• 71fdf93 chore(deps-dev): bump the lint group with 9 updates (#183)
• e19e66c chore(deps-dev): bump the development group with 3 updates (#181)
• 9c9fb62 chore(deps-dev): bump the lint group with 10 updates (#178)
• 2e9724f chore(deps-dev): bump the development group with 5 updates (#176)
• fe58a59 chore(deps): bump actions/upload-artifact from 3 to 4 (#172)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)