Update JS-DevTools/npm-publish action to v4 by renovate[bot] · Pull Request #26 · adobe/apollo-link-mutation-queue

renovate · 2025-09-15T04:02:49Z

This PR contains the following updates:

Package	Type	Update	Change
JS-DevTools/npm-publish	action	major	`v1` → `v4`

Release Notes

JS-DevTools/npm-publish (JS-DevTools/npm-publish)

`v4.1.5`

Compare Source

- uses: JS-DevTools/npm-publish@v4.1.5

Bug fixes

deps: bump the production group with 2 updates (#261) (3c4834c)

`v4.1.4`

Compare Source

- uses: JS-DevTools/npm-publish@v4.1.4

Bug fixes

deps: bump tar from 7.5.2 to 7.5.3 (#260) (57836fb)

`v4.1.3`

Compare Source

- uses: JS-DevTools/npm-publish@v4.1.3

Bug fixes

add sourcemap back to tracking (#259) (d2fef91)

`v4.1.2`

Compare Source

- uses: JS-DevTools/npm-publish@v4.1.2

Bug fixes

deps: bump the production group with 3 updates (#252) (43babc0)

`v4.1.1`

Compare Source

- uses: JS-DevTools/npm-publish@v4.1.1

Bug fixes

bump tar from 7.4.3 to 7.5.1 (#249) (99ef290)

`v4.1.0`

Compare Source

- uses: JS-DevTools/npm-publish@v4.1.0

Features

allow token to be optional for OIDC-based publish (#247) (612922f), closes #242

`v4.1`

Compare Source

`v4.0.1`

Compare Source

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

Bug fixes

do not suppress E409 from npm publish (#246) (c13368d), closes #245

`v4.0.0`

Compare Source

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)

Bug fixes

include registry URL pathname in npm config (#186)

`v3.1.0`

Compare Source

Features

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

Performance Improvements

action: decrease bundle size (#166)

`v3.1`

Compare Source

`v3.0.1`

Compare Source

Bug fixes

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

`v3.0.0`

Compare Source

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)

`v3.0`

Compare Source

`v3`

Compare Source

`v2.2.2`

Compare Source

Bug Fixes

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

`v2.2.1`

Compare Source

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`

Compare Source

Features

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

`v2.2`

Compare Source

`v2.1.0`

Compare Source

Features

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

Bug Fixes

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

`v2.1`

Compare Source

`v2.0.0`

Compare Source

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.
```
  with:
    token: ${{ secrets.NPM_TOKEN }}
-   check-version: true
-   greater-version-only: false
+   strategy: all
```
- Use strategy: upgrade to only publish versions that upgrade the selected tag.
```
  with:
    token: ${{ secrets.NPM_TOKEN }}
-   check-version: true
-   greater-version-only: true
+   strategy: upgrade
```
- check-version: false has been removed. You don't need this action if you're not checking already published versions; use npm directly, instead.
The library and CLI now require Node v16 or later. They may technically work in earlier versions, but they're not tested in CI and you will have to tell your package manager to ignore the engines requirement.
The library and CLI no longer read the user's ~/.npmrc file, so the token option is now required.

Features

tag, access, and registry now fall back to publishConfig in package.json, if specified. (#36)
The package argument may now be a directory, and is passed to npm publish as its package_spec argument. (#59)
The package argument may also be a pre-packed .tgz archive (#81)

Bug fixes

The user's ~/.npmrc file is no longer modified. Instead, a temporary .npmrc file is used. (#15)
npm is now always called with --ignore-scripts for security (#47)
npm is now always called in the current working directory (#51)
The action was updated to use the Node v16 runtime. (#61)
The @actions/core dependency was upgraded to fix deprecation warnings. (#67)

`v2.0`

Compare Source

`v2`

Compare Source

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

chore(deps): update js-devtools/npm-publish action to v4

f4a11e4

renovate Bot changed the title ~~chore(deps): update js-devtools/npm-publish action to v4~~ Update JS-DevTools/npm-publish action to v4 Apr 15, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update JS-DevTools/npm-publish action to v4#26

Update JS-DevTools/npm-publish action to v4#26
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/js-devtools-npm-publish-4.x

renovate Bot commented Sep 15, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate Bot commented Sep 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Bug fixes

Features

Bug fixes

⚠ BREAKING CHANGES

Features

Bug Fixes

Code Refactoring

Bug fixes

Features

Performance Improvements

Bug fixes

BREAKING CHANGES

Bug fixes

Bug Fixes

Bug Fixes

Features

Features

Bug Fixes

BREAKING CHANGES

Features

Bug fixes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Sep 15, 2025 •

edited

Loading