[PR #2821] [MERGED] Bump JS-DevTools/npm-publish from 1 to 2 #3819

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/electerm/electerm/pull/2821
Author: @dependabot[bot]
Created: 4/20/2023
Status: ✅ Merged
Merged: 5/4/2023
Merged by: @zxdong262

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

📝 Commits (1)

439b341 Bump JS-DevTools/npm-publish from 1 to 2

📊 Changes

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

View changed files

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

📄 Description

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

Release notes

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

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.
  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)

Changelog

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

Commits

0be441d Update to version 2 (#84)
a102974 Add tarball package publish (#85)
c5f37b9 Rewrite internals for v2 release (#83)
b992c2e Upgrade TypeScript and ESLint (#79)
bfc489d Switch build system from ncc to esbuild (#75)
43fca1b Change main branch to main (#82)
3ee021c Add end-to-end test suite (#80)
d6a8488 Upgrade semver (#77)
1641d03 Upgrade action to Node v16 and actions/core to v1.10 (#68)
71869b5 Remove dependencies status badge from README (#50)
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 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/2821 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 4/20/2023 **Status:** ✅ Merged **Merged:** 5/4/2023 **Merged by:** [@zxdong262](https://github.com/zxdong262) **Base:** `master` ← **Head:** `dependabot/github_actions/JS-DevTools/npm-publish-2` --- ### 📝 Commits (1) - [`439b341`](https://github.com/electerm/electerm/commit/439b341c15f02dd9d585ac04bb9444add2d8c749) Bump JS-DevTools/npm-publish from 1 to 2 ### 📊 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 1 to 2. <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>v2.0.0</h2> <p>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!</p> <h2>BREAKING CHANGES</h2> <ul> <li> <p>The <code>type</code> output is now an empty string instead of <code>none</code> when no release occurs</p> <pre lang="diff"><code>- - if: ${{ steps.publish.outputs.type != 'none' }} + - if: ${{ steps.publish.outputs.type }} run: echo "Version changed!" </code></pre> </li> <li> <p>The <code>check-version</code> and <code>greater-version-only</code> options have been removed and replaced with <code>strategy</code>.</p> <ul> <li>Use <code>strategy: all</code> (default) to publish all versions that do not yet exist in the registry. <pre lang="diff"><code> with: token: ${{ secrets.NPM_TOKEN }} - check-version: true - greater-version-only: false + strategy: all </code></pre> </li> <li>Use <code>strategy: upgrade</code> to only publish versions that upgrade the selected tag. <pre lang="diff"><code> with: token: ${{ secrets.NPM_TOKEN }} - check-version: true - greater-version-only: true + strategy: upgrade </code></pre> </li> <li><code>check-version: false</code> has been removed. You don't need this action if you're not checking already published versions; use <code>npm</code> directly, instead.</li> </ul> </li> <li> <p>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 <code>engines</code> requirement.</p> </li> <li> <p>The library and CLI no longer read the user's <code>~/.npmrc</code> file, so the <code>token</code> option is now required.</p> </li> </ul> <h2>Features</h2> <ul> <li><code>tag</code>, <code>access</code>, and <code>registry</code> now fall back to <code>publishConfig</code> in <code>package.json</code>, if specified. (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/36">#36</a>)</li> <li>The <code>package</code> argument may now be a directory, and is passed to <code>npm publish</code> as its <code>package_spec</code> argument. (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/59">#59</a>)</li> <li>The <code>package</code> argument may also be a pre-packed <code>.tgz</code> archive (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/81">#81</a>)</li> </ul> <h2>Bug fixes</h2> <ul> <li>The user's <code>~/.npmrc</code> file is no longer modified. Instead, a temporary <code>.npmrc</code> file is used. (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/15">#15</a>)</li> <li><code>npm</code> is now always called with <code>--ignore-scripts</code> for security (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/47">#47</a>)</li> <li><code>npm</code> is now always called in the current working directory (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/51">#51</a>)</li> <li>The action was updated to use the Node v16 runtime. (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/61">#61</a>)</li> <li>The <code>@actions/core</code> dependency was upgraded to fix deprecation warnings. (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/67">#67</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> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/0be441d808570461daedc3fb178405dbcac54de0"><code>0be441d</code></a> Update to version 2 (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/84">#84</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/a10297455a5b4049ad8e88580ab789b32b96ee04"><code>a102974</code></a> Add tarball package publish (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/85">#85</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/c5f37b90eac9e430a3af0b211f80efb9b191bd8c"><code>c5f37b9</code></a> Rewrite internals for v2 release (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/83">#83</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/b992c2e1ba643d38b8a937a5c70587fdd70fbc21"><code>b992c2e</code></a> Upgrade TypeScript and ESLint (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/79">#79</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/bfc489d8a29dae7a1a59e5c59dbe1bb5215260f1"><code>bfc489d</code></a> Switch build system from ncc to esbuild (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/75">#75</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/43fca1b61baf2dd6a1079835450b7ff3841d2664"><code>43fca1b</code></a> Change main branch to <code>main</code> (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/82">#82</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/3ee021c43fcf5aa1baf051e0b727b991ddbb9de6"><code>3ee021c</code></a> Add end-to-end test suite (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/80">#80</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/d6a8488a9d6529b37523120e7326b26c748f8194"><code>d6a8488</code></a> Upgrade semver (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/77">#77</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/1641d030cee266f093503c555ee9303ae7aede16"><code>1641d03</code></a> Upgrade action to Node v16 and actions/core to v1.10 (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/68">#68</a>)</li> <li><a href="https://github.com/JS-DevTools/npm-publish/commit/71869b5f0195f8c289f623103692895dd046d50d"><code>71869b5</code></a> Remove dependencies status badge from README (<a href="https://redirect.github.com/JS-DevTools/npm-publish/issues/50">#50</a>)</li> <li>Additional commits viewable in <a href="https://github.com/JS-DevTools/npm-publish/compare/v1...v2">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=1&new-version=2)](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 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>