[PR #3044] [MERGED] Bump JS-DevTools/npm-publish from 2 to 3 #3855

New issue

Closed

opened 2026-02-27 01:54:02 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 01:54:02 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/electerm/electerm/pull/3044
Author: @dependabot[bot]
Created: 10/19/2023
Status: ✅ Merged
Merged: 10/21/2023
Merged by: @zxdong262

Base: master ← Head: dependabot/github_actions/JS-DevTools/npm-publish-3

📝 Commits (1)

7a22cdc Bump JS-DevTools/npm-publish from 2 to 3

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 .github/workflows/npm.yml (+1 -1)

📄 Description

Bumps JS-DevTools/npm-publish from 2 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 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

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

6fd3bc8 fix!(action): update runtime to Node.js v20 (#150)
7f426c9 chore(deps): bump the lint group with 7 updates (#159)
806badd chore(deps-dev): bump the development group with 4 updates (#156)
See full diff 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)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/electerm/electerm/pull/3044 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 10/19/2023 **Status:** ✅ Merged **Merged:** 10/21/2023 **Merged by:** [@zxdong262](https://github.com/zxdong262) **Base:** `master` ← **Head:** `dependabot/github_actions/JS-DevTools/npm-publish-3` --- ### 📝 Commits (1) - [`7a22cdc`](https://github.com/electerm/electerm/commit/7a22cdc52cadc580c78daa2d5dc68522fa3a8889) Bump JS-DevTools/npm-publish from 2 to 3 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/npm.yml` (+1 -1) </details> ### 📄 Description Bumps [JS-DevTools/npm-publish](https://github.com/js-devtools/npm-publish) from 2 to 3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/js-devtools/npm-publish/releases">JS-DevTools/npm-publish's releases</a>.</em></p> <blockquote> <h2>v3.0.0</h2> <p>The v3 release updates the action's runtime to Node.js v20, but otherwise, there are are no public API changes.</p> <h2>BREAKING CHANGES</h2> <ul> <li>The action will now run on Node.js v20 instead of v16</li> </ul> <h2>Bug fixes</h2> <ul> <li><strong>action</strong>: update runtime to Node.js v20 (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/150">#150</a>)</li> </ul> <h2>v2.2.2</h2> <h2>Bug Fixes</h2> <ul> <li>use validated <code>package.json</code> version for comparisons (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/147">#147</a>), closes <a href="https://redirect.github.com/js-devtools/npm-publish/issues/139">#139</a></li> </ul> <h2>v2.2.1</h2> <h2>Bug Fixes</h2> <ul> <li><strong>action</strong>: update semver dep, esbuild and vitest dev deps (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/114">#114</a>)</li> <li><strong>npm</strong>: do not assume error code is a string (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/120">#120</a>), closes <a href="https://redirect.github.com/js-devtools/npm-publish/issues/119">#119</a></li> </ul> <h2>v2.2.0</h2> <h2>Features</h2> <ul> <li>Allow <code>--ignore-scripts</code> to be disabled in order to support publish lifecycle hooks (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/102">#102</a>)</li> </ul> <h2>v2.1.0</h2> <h2>Features</h2> <ul> <li>Add explicit support for <code>--provenance</code> (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/92">#92</a>), closes <a href="https://redirect.github.com/js-devtools/npm-publish/issues/88">#88</a></li> </ul> <h2>Bug Fixes</h2> <ul> <li>Handle missing <code>latest</code> tag during version check (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/90">#90</a>), closes <a href="https://redirect.github.com/js-devtools/npm-publish/issues/89">#89</a></li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/JS-DevTools/npm-publish/blob/main/CHANGELOG.md">JS-DevTools/npm-publish's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/JS-DevTools/npm-publish/tree/v1.4.0">v1.4.0</a> (2020-10-02)</h2> <ul> <li> <p>Added support NPM's <code>--tag</code> argument, which allows packages to be published to a named tag that can then be installed using <code>npm install <package-name>@<tag></code></p> </li> <li> <p>Added support for NPM's <code>--access</code> argument, which controls whether scoped packages are publicly accessible, or restricted to members of your NPM organization</p> </li> </ul> <p><a href="https://github.com/JS-DevTools/npm-publish/compare/v1.3.0...v1.4.0">Full Changelog</a></p> <h2><a href="https://github.com/JS-DevTools/npm-publish/tree/v1.3.0">v1.3.0</a> (2020-10-01)</h2> <ul> <li>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 <a href="https://redirect.github.com/js-devtools/npm-publish/issues/12">#12</a>](<a href="https://redirect.github.com/JS-DevTools/npm-publish/pull/12">JS-DevTools/npm-publish#12</a>) from <a href="https://github.com/ZitRos"><code>@ZitRos</code></a>)</li> </ul> <p><a href="https://github.com/JS-DevTools/npm-publish/compare/v1.2.0...v1.3.0">Full Changelog</a></p> <h2><a href="https://github.com/JS-DevTools/npm-publish/tree/v1.2.0">v1.2.0</a> (2020-07-23)</h2> <ul> <li>Added support for running NPM in "dry run" mode, which doesn't actually publish, but reports details of what <em>would</em> have been published.</li> </ul> <p><a href="https://github.com/JS-DevTools/npm-publish/compare/v1.1.2...v1.2.0">Full Changelog</a></p> <h2><a href="https://github.com/JS-DevTools/npm-publish/tree/v1.1.0">v1.1.0</a> (2020-03-29)</h2> <ul> <li>FIX: The configured NPM registry and token are now used <em>all</em> NPM commands, not just for publishing. This ensures that npm-publish works with private packages and custom registries</li> </ul> <p><a href="https://github.com/JS-DevTools/npm-publish/compare/v1.0.13...v1.1.0">Full Changelog</a></p> <h2><a href="https://github.com/JS-DevTools/npm-publish/tree/v1.0.0">v1.0.0</a> (2020-01-21)</h2> <p>Initial release 🎉</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/6fd3bc8dad0cb1a484731fe6486a03193f98f037"><code>6fd3bc8</code></a> fix!(action): update runtime to Node.js v20 (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/150">#150</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/7f426c9ea8cd6f53975623a350c34e3a3707739c"><code>7f426c9</code></a> chore(deps): bump the lint group with 7 updates (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/159">#159</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/806badd32f13bcd33cf4a4a2efc00eb68bfcc89f"><code>806badd</code></a> chore(deps-dev): bump the development group with 4 updates (<a href="https://redirect.github.com/js-devtools/npm-publish/issues/156">#156</a>)</li> <li>See full diff in <a href="https://github.com/js-devtools/npm-publish/compare/v2...v3">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=JS-DevTools/npm-publish&package-manager=github_actions&previous-version=2&new-version=3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>