ci: bump JS-DevTools/npm-publish from 3 to 4

[dependabot]

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

Release notes

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

v4.0.0

The v4 release updates the action runtime to Node 24, but there have been no usage changes to the action.

Immutable releases have been enabled for this repository. As a security practice, we recommend pinning to an exact release:

- uses: JS-DevTools/npm-publish@v4.0.0
  with:
    token: ${{ secrets.NPM_TOKEN }}

⚠ BREAKING CHANGES

• The action now runs on Node 24 with npm 11
• The library and CLI now require Node >= 20, Node 16 and 18 are no longer supported
• The library is now ESM only

Features

• update action runtime to Node 24 (#231) (0b36106)

Bug Fixes

• deps: bump the production group across 1 directory with 5 updates (#238) (314ae61)
• deps: update tar and semver dependencies (#194) (cd26c94)
• update dry-run and publish conflict logic for npm>=10 (#232) (62716ea)
• windows: allow spawning npm cli on windows (#199) (f45e793), closes #198

Code Refactoring

• switch module format to ESM (#234) (e081941)

v3.1.1

Bug fixes

• include registry URL pathname in npm config (#186)

v3.1.0

Features

• dry-run: always print publish results in dry run (#185), closes #184

Performance Improvements

• action: decrease bundle size (#166)

v3.0.1

Bug fixes

• errors: improve message when version validation fails (#161), closes #160

Changelog

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

Change Log (Archived)

See releases for current change log.

---

All notable changes will be documented in this file. NPM Publish adheres to Semantic Versioning.

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

Commits

• 0fd2f43 chore(release): 4.1.5
• 3c4834c fix(deps): bump the production group with 2 updates (#261)
• 22291ed build(deps-dev): bump the development group with 6 updates (#262)
• 4ce4bd0 chore(release): 4.1.4
• 57836fb fix(deps): bump tar from 7.5.2 to 7.5.3 (#260)
• d2fef91 chore(release): 4.1.3
• 3eb8411 fix: add sourcemap back to tracking (#259)
• 8f08ec0 chore(release): 4.1.2
• 43babc0 fix(deps): bump the production group with 3 updates (#252)
• 764af68 docs(readme): switch main example to trusted publishing (#257)
• 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 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)

[dependabot]

Looks like JS-DevTools/npm-publish is no longer a dependency, so this is no longer needed.