github-starred/awesome-cryptography
2
0
Fork 0
mirror of https://github.com/sobolevn/awesome-cryptography.git synced 2026-07-18 11:32:21 -05:00
Code Issues 1.2k Packages Projects Releases Wiki Activity

[PR #167] [MERGED] Bump actions/setup-node from 2 to 3 #6379

New Issue
Closed
opened 2026-07-14 00:55:59 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-07-14 00:55:59 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/sobolevn/awesome-cryptography/pull/167
Author: @dependabot[bot]
Created: 2/28/2022
Status: ✅ Merged
Merged: 2/28/2022
Merged by: @sobolevn

Base: master ← Head: dependabot/github_actions/actions/setup-node-3

📝 Commits (1)

  • ef76a92 Bump actions/setup-node from 2 to 3

📊 Changes

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

View changed files

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

📄 Description

Bumps actions/setup-node from 2 to 3.

Release notes

Sourced from actions/setup-node's releases.

v3.0.0

In scope of this release we changed version of the runtime Node.js for the setup-node action and updated package-lock.json file to v2.

Breaking Changes

Fix logic of error handling for npm warning and uncaught exception

In scope of this release we fix logic of error handling related to caching (actions/setup-node#358) and (actions/setup-node#359).

In the previous behaviour we relied on stderr output to throw error. The warning messages from package managers can be written to the stderr's output. For now the action will throw an error only if exit code differs from zero. Besides, we add logic to сatch and log unhandled exceptions.

Adding Node.js version file support

In scope of this release we add the node-version-file input and update actions/cache dependency to the latest version.

Adding Node.js version file support

The new input (node-version-file) provides functionality to specify the path to the file containing Node.js's version with such behaviour:

  • If the file does not exist the action will throw an error.
  • If you specify both node-version and node-version-file inputs, the action will use value from the node-version input and throw the following warning: Both node-version and node-version-file inputs are specified, only node-version will be used.
  • For now the action does not support all of the variety of values for Node.js version files. The action can handle values according to the documentation and values with v prefix (v14)
steps:
  - uses: actions/checkout@v2
  - name: Setup node from node version file
    uses: actions/setup-node@v2
    with:
      node-version-file: '.nvmrc'
  - run: npm install
  - run: npm test

Update actions/cache dependency to 1.0.8 version.

We updated actions/cache dependency to the latest version (1.0.8). For more information please refer to the toolkit/cache.

Add "cache-hit" output

This release introduces a new output: cache-hit (#327).

The cache-hit output contains boolean value indicating that an exact match was found for the key. It shows that the action uses already existing cache or not. The output is available only if cache is enabled.

Support caching for mono repos and repositories with complex structure

This release introduces dependency caching support for mono repos and repositories with complex structure (#305).

By default, the action searches for the dependency file (package-lock.json or yarn.lock) in the repository root. Use the cache-dependency-path input for cases when multiple dependency files are used, or they are located in different subdirectories. This input supports wildcards or a list of file names for caching multiple dependencies.

Yaml example:

steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
</tr></table>

... (truncated)

Commits

Dependabot compatibility score

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/sobolevn/awesome-cryptography/pull/167 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 2/28/2022 **Status:** ✅ Merged **Merged:** 2/28/2022 **Merged by:** [@sobolevn](https://github.com/sobolevn) **Base:** `master` ← **Head:** `dependabot/github_actions/actions/setup-node-3` --- ### 📝 Commits (1) - [`ef76a92`](https://github.com/sobolevn/awesome-cryptography/commit/ef76a920068831ecd3ce7fecfa2b099879c8f75b) Bump actions/setup-node from 2 to 3 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/test.yml` (+1 -1) </details> ### 📄 Description Bumps [actions/setup-node](https://github.com/actions/setup-node) from 2 to 3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/setup-node/releases">actions/setup-node's releases</a>.</em></p> <blockquote> <h2>v3.0.0</h2> <p>In scope of this release we changed version of the runtime Node.js for the setup-node action and updated package-lock.json file to v2.</p> <h3>Breaking Changes</h3> <ul> <li>With the update to Node 16 in <a href="https://github-redirect.dependabot.com/actions/setup-node/pull/414">actions/setup-node#414</a>, all scripts will now be run with Node 16 rather than Node 12.</li> <li>We removed deprecated <code>version</code> input (<a href="https://github-redirect.dependabot.com/actions/setup-node/pull/424">actions/setup-node#424</a>). Please use <code>node-version</code> input instead.</li> </ul> <h2>Fix logic of error handling for npm warning and uncaught exception</h2> <p>In scope of this release we fix logic of error handling related to caching (<a href="https://github-redirect.dependabot.com/actions/setup-node/pull/358">actions/setup-node#358</a>) and (<a href="https://github-redirect.dependabot.com/actions/setup-node/pull/359">actions/setup-node#359</a>).</p> <p>In the previous behaviour we relied on <code>stderr</code> output to throw error. The warning messages from package managers can be written to the stderr's output. For now the action will throw an error only if exit code differs from zero. Besides, we add logic to сatch and log unhandled exceptions.</p> <h2>Adding Node.js version file support</h2> <p>In scope of this release we add the <code>node-version-file</code> input and update <code>actions/cache</code> dependency to the latest version.</p> <h2>Adding Node.js version file support</h2> <p>The new input (<code>node-version-file</code>) provides functionality to specify the path to the file containing Node.js's version with such behaviour:</p> <ul> <li>If the file does not exist the action will throw an error.</li> <li>If you specify both <code>node-version</code> and <code>node-version-file</code> inputs, the action will use value from the <code>node-version</code> input and throw the following warning: <code>Both node-version and node-version-file inputs are specified, only node-version will be used</code>.</li> <li>For now the action does not support all of the variety of values for Node.js version files. The action can handle values according to the <a href="https://github.com/actions/setup-node#supported-version-syntax">documentation</a> and values with <code>v</code> prefix (<code>v14</code>)</li> </ul> <pre lang="yaml"><code>steps: - uses: actions/checkout@v2 - name: Setup node from node version file uses: actions/setup-node@v2 with: node-version-file: '.nvmrc' - run: npm install - run: npm test </code></pre> <h2>Update actions/cache dependency to 1.0.8 version.</h2> <p>We updated actions/cache dependency to the latest version (1.0.8). For more information please refer to the <a href="https://github.com/actions/toolkit/blob/main/packages/cache/RELEASES.md">toolkit/cache</a>.</p> <h2>Add &quot;cache-hit&quot; output</h2> <p>This release introduces a new output: <code>cache-hit</code> (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/327">#327</a>).</p> <p>The <code>cache-hit</code> output contains boolean value indicating that an exact match was found for the key. It shows that the action uses already existing cache or not. The output is available only if cache is enabled.</p> <h2>Support caching for mono repos and repositories with complex structure</h2> <p>This release introduces dependency caching support for mono repos and repositories with complex structure (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/305">#305</a>).</p> <p>By default, the action searches for the dependency file (<code>package-lock.json</code> or <code>yarn.lock</code>) in the repository root. Use the <code>cache-dependency-path</code> input for cases when multiple dependency files are used, or they are located in different subdirectories. This input supports wildcards or a list of file names for caching multiple dependencies.</p> <p>Yaml example:</p> <pre lang="yml"><code>steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 &lt;/tr&gt;&lt;/table&gt; </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/setup-node/commit/9ced9a43a244f3ac94f13bfd896db8c8f30da67a"><code>9ced9a4</code></a> remove version input (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/424">#424</a>)</li> <li><a href="https://github.com/actions/setup-node/commit/3e90744edfed8715c51c59ca546063d5d3035443"><code>3e90744</code></a> Update lockfileVersion (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/422">#422</a>)</li> <li><a href="https://github.com/actions/setup-node/commit/28df918a562341c61f4849bb5b0cae0da42e9ff8"><code>28df918</code></a> Update default runtime to node16 (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/414">#414</a>)</li> <li><a href="https://github.com/actions/setup-node/commit/f099707f6e7a91b89cdebdeca599fc76cc8bf088"><code>f099707</code></a> fix tsc build error for <code>@​actions/http-client</code> (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/402">#402</a>)</li> <li><a href="https://github.com/actions/setup-node/commit/f658dc5bd7deff7ab8a4bfa9ccb65a6540175be2"><code>f658dc5</code></a> ci: use NPM cache in check-dist (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/393">#393</a>)</li> <li><a href="https://github.com/actions/setup-node/commit/5e2e06871487f1c1f2806100f6ad85acf4bce48d"><code>5e2e068</code></a> ci(workflow): add cache to workflows using actions/setup-node (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/287">#287</a>)</li> <li><a href="https://github.com/actions/setup-node/commit/7a0f7a99626ad9d2e3bcc28dce6c379216703cc3"><code>7a0f7a9</code></a> Fix grammar in the README (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/331">#331</a>)</li> <li><a href="https://github.com/actions/setup-node/commit/7b558676dd6f955a469559a6f9db9e0447fe8749"><code>7b55867</code></a> chore: Remove strategy for non-matrix builds (<a href="https://github-redirect.dependabot.com/actions/setup-node/issues/186">#186</a>)</li> <li>See full diff in <a href="https://github.com/actions/setup-node/compare/v2...v3">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/setup-node&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 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>
GiteaMirror added the pull-request label 2026-07-14 00:55:59 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
content-request
enhancement
foreign-invalid-link
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
section-request
waits-feedback
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-cryptography#6379
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?