Trez/ultima-ai
4
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Activity

🔧 Renovate: Update (minor) actions/setup-node action to v2.5.2 #101

Closed
renovate-bot wants to merge 1 commits from renovate/github-actions-actions-setup-node-v2-5-2 into main
pull from: renovate/github-actions-actions-setup-node-v2-5-2
merge into: Trez:main
Conversation 1 Commits 1 Files Changed 1
+1 -1
renovate-bot commented 2026-01-24 11:03:55 -05:00
Member
Copy Link
Copy Source

This PR contains the following updates:

Package Type Update Change
actions/setup-node action minor v2 → v2.5.2

⚡ Renovate Update Info

  • Update Type: minor

  • Automerge: 🛑 This update requires manual approval

Release Notes

actions/setup-node (actions/setup-node)

v2.5.2: Update @​actions/core for v2

Compare Source

In scope of this release we updated actions/core to 1.10.0 and actions/tool-cache to 1.7.2 for v2: #​713

v2.5.1: Fix logic of error handling for npm warning and uncaught exception

Compare Source

In scope of this release we fix logic of error handling related to caching (#​358) and (#​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.

v2.5.0: Adding Node.js version file support

Compare Source

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.

v2.4.1: Add "cache-hit" output

Compare Source

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.

v2.4.0: Support caching for mono repos and repositories with complex structure

Compare Source

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
  with:
    node-version: 14
    cache: npm
    cache-dependency-path: 'sub-project/package-lock.json'

For more examples of using cache-dependency-path input, see the Advanced usage guide.

v2.3.2: Revert temporary fix

Compare Source

We had to disable pre-cached Node.js usage in the previous version due to the broken image cache. Now cache is fixed, so we can safely enable its usage again.
Thank you for understanding.

v2.3.1: Temporary maintenance fix.

Compare Source

Temporarily disabled usage of pre-cached Node.js.

v2.3.0: Support caching pnpm dependencies

Compare Source

This release introduces dependency caching support for the pnpm package manager (#​278).

Caching pnpm dependencies:


# This workflow uses actions that are not certified by GitHub.
# They are provided by a third-party and are governed by

# separate terms of service, privacy policy, and support
# documentation.

steps:
- uses: actions/checkout@v2
- uses: pnpm/action-setup@646cdf48217256a3d0b80361c5a50727664284f2
  with:
    version: 6.10.0
- uses: actions/setup-node@v2
  with:
    node-version: '14'
    cache: 'pnpm'
- run: pnpm install
- run: pnpm test

NOTE: pnpm caching support requires pnpm version >= 6.10.0

v2.2.0: Support caching dependencies and LTS aliases

Compare Source

This release brings two major features:

Supported version syntax

The node-version input supports the following syntax:

major versions: 12, 14, 16
more specific versions: 10.15, 14.2.0, 16.3.0
nvm LTS syntax: lts/erbium, lts/fermium, lts/*

Caching dependencies

The action has a built-in functionality for caching and restoring npm/yarn dependencies. Supported package managers are npm, yarn. The cache input is optional, and caching is turned off by default.

Caching npm dependencies:

steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
  with:
    node-version: '14'
    cache: 'npm'
- run: npm install
- run: npm test

Caching yarn dependencies:

steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
  with:
    node-version: '14'
    cache: 'yarn'
- run: yarn install
- run: yarn test

Yarn caching handles both yarn versions: 1 or 2.

At the moment, only lock files in the project root are supported.

v2.1.5: Release

Compare Source

Improve error and warning line number handling (problem matcher regex)

v2.1.4

Compare Source

The first stable release of actions/setup-node V2

v2.1.3: (beta)

Compare Source

  • Add support for specifying architecture of Node.JS

v2.1.2: (beta)

Compare Source

  • Updated communication with runner to use environment files rather then workflow commands

v2.1.1: (beta)

Compare Source

Switch to main branch of node-versions repository to consume latest added versions.

v2.1.0: (beta)

Compare Source

Added check-latest input option to query the versions manifest for latest version before checking for semver match in local VM cache first (the default). That's useful for ensuring you get latest as soon as it's released to the cache but at the cost of perf / reliability (much more likely to incur and download and extract).

Configuration

📅 Schedule: Branch creation - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/setup-node](https://github.com/actions/setup-node) | action | minor | `v2` → `v2.5.2` | ### ⚡ Renovate Update Info - **Update Type:** minor - **Automerge:** 🛑 This update requires manual approval --- ### Release Notes <details> <summary>actions/setup-node (actions/setup-node)</summary> ### [`v2.5.2`](https://github.com/actions/setup-node/releases/tag/v2.5.2): Update @&#8203;actions/core for v2 [Compare Source](https://github.com/actions/setup-node/compare/v2.5.1...v2.5.2) In scope of this release we updated actions/core to 1.10.0 and actions/tool-cache to 1.7.2 for v2: [#&#8203;713](https://github.com/actions/setup-node/pull/713) ### [`v2.5.1`](https://github.com/actions/setup-node/releases/tag/v2.5.1): Fix logic of error handling for npm warning and uncaught exception [Compare Source](https://github.com/actions/setup-node/compare/v2.5.0...v2.5.1) In scope of this release we fix logic of error handling related to caching ([#&#8203;358](https://github.com/actions/setup-node/pull/358)) and ([#&#8203;359](https://github.com/actions/setup-node/pull/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. ### [`v2.5.0`](https://github.com/actions/setup-node/releases/tag/v2.5.0): Adding Node.js version file support [Compare Source](https://github.com/actions/setup-node/compare/v2.4.1...v2.5.0) 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](https://github.com/actions/setup-node#supported-version-syntax) and values with `v` prefix (`v14`) ```yaml 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](https://github.com/actions/toolkit/blob/main/packages/cache/RELEASES.md). ### [`v2.4.1`](https://github.com/actions/setup-node/releases/tag/v2.4.1): Add &quot;cache-hit&quot; output [Compare Source](https://github.com/actions/setup-node/compare/v2.4.0...v2.4.1) This release introduces a new output: `cache-hit` ([#&#8203;327](https://github.com/actions/setup-node/issues/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. ### [`v2.4.0`](https://github.com/actions/setup-node/releases/tag/v2.4.0): Support caching for mono repos and repositories with complex structure [Compare Source](https://github.com/actions/setup-node/compare/v2.3.2...v2.4.0) This release introduces dependency caching support for mono repos and repositories with complex structure ([#&#8203;305](https://github.com/actions/setup-node/issues/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: ```yml steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: 14 cache: npm cache-dependency-path: 'sub-project/package-lock.json' ``` For more examples of using `cache-dependency-path` input, see the [Advanced usage](https://github.com/actions/setup-node/blob/25316bbc1f10ac9d8798711f44914b1cf3c4e954/docs/advanced-usage.md#caching-packages-dependencies) guide. ### [`v2.3.2`](https://github.com/actions/setup-node/releases/tag/v2.3.2): Revert temporary fix [Compare Source](https://github.com/actions/setup-node/compare/v2.3.1...v2.3.2) We had to disable pre-cached Node.js usage in the previous version due to the broken image cache. Now cache is fixed, so we can safely enable its usage again. Thank you for understanding. ### [`v2.3.1`](https://github.com/actions/setup-node/releases/tag/v2.3.1): Temporary maintenance fix. [Compare Source](https://github.com/actions/setup-node/compare/v2.3.0...v2.3.1) Temporarily disabled usage of pre-cached Node.js. ### [`v2.3.0`](https://github.com/actions/setup-node/releases/tag/v2.3.0): Support caching pnpm dependencies [Compare Source](https://github.com/actions/setup-node/compare/v2.2.0...v2.3.0) This release introduces dependency caching support for the `pnpm` package manager ([#&#8203;278](https://github.com/actions/setup-node/issues/278)). **Caching pnpm dependencies:** ```yaml # This workflow uses actions that are not certified by GitHub. # They are provided by a third-party and are governed by # separate terms of service, privacy policy, and support # documentation. steps: - uses: actions/checkout@v2 - uses: pnpm/action-setup@646cdf48217256a3d0b80361c5a50727664284f2 with: version: 6.10.0 - uses: actions/setup-node@v2 with: node-version: '14' cache: 'pnpm' - run: pnpm install - run: pnpm test ``` **NOTE**: pnpm caching support requires pnpm version >= 6.10.0 ### [`v2.2.0`](https://github.com/actions/setup-node/releases/tag/v2.2.0): Support caching dependencies and LTS aliases [Compare Source](https://github.com/actions/setup-node/compare/v2.1.5...v2.2.0) This release brings two major features: - [Support LTS aliases #&#8203;270](https://github.com/actions/setup-node/pull/270) - [Implementation of node's caching #&#8203;272](https://github.com/actions/setup-node/pull/272) ##### Supported version syntax The `node-version` input supports the following syntax: major versions: `12`, `14`, `16`\ more specific versions: `10.15`, `14.2.0`, `16.3.0`\ nvm LTS syntax: `lts/erbium`, `lts/fermium`, `lts/*` ##### Caching dependencies The action has a built-in functionality for caching and restoring npm/yarn dependencies. Supported package managers are `npm`, `yarn`. The `cache` input is optional, and caching is turned off by default. **Caching npm dependencies:** ```yaml steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: '14' cache: 'npm' - run: npm install - run: npm test ``` **Caching yarn dependencies:** ```yaml steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: '14' cache: 'yarn' - run: yarn install - run: yarn test ``` Yarn caching handles both yarn versions: 1 or 2. > At the moment, only `lock` files in the project root are supported. ### [`v2.1.5`](https://github.com/actions/setup-node/releases/tag/v2.1.5): Release [Compare Source](https://github.com/actions/setup-node/compare/v2.1.4...v2.1.5) Improve error and warning line number handling (problem matcher regex) ### [`v2.1.4`](https://github.com/actions/setup-node/releases/tag/v2.1.4) [Compare Source](https://github.com/actions/setup-node/compare/v2.1.3...v2.1.4) The first stable release of actions/setup-node V2 ### [`v2.1.3`](https://github.com/actions/setup-node/releases/tag/v2.1.3): (beta) [Compare Source](https://github.com/actions/setup-node/compare/v2.1.2...v2.1.3) - Add support for specifying architecture of Node.JS ### [`v2.1.2`](https://github.com/actions/setup-node/releases/tag/v2.1.2): (beta) [Compare Source](https://github.com/actions/setup-node/compare/v2.1.1...v2.1.2) - Updated communication with runner to use environment files rather then workflow commands ### [`v2.1.1`](https://github.com/actions/setup-node/releases/tag/v2.1.1): (beta) [Compare Source](https://github.com/actions/setup-node/compare/v2.1.0...v2.1.1) Switch to `main` branch of [node-versions](https://github.com/actions/node-versions) repository to consume latest added versions. ### [`v2.1.0`](https://github.com/actions/setup-node/releases/tag/v2.1.0): (beta) [Compare Source](https://github.com/actions/setup-node/compare/v2...v2.1.0) Added check-latest input option to query the versions manifest for latest version before checking for semver match in local VM cache first (the default). That's useful for ensuring you get latest as soon as it's released to the cache but at the cost of perf / reliability (much more likely to incur and download and extract). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi44NC4yIiwidXBkYXRlZEluVmVyIjoiNDIuODQuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIiwicmVub3ZhdGUiXX0=-->
renovate-bot added the dependenciesrenovate labels 2026-01-24 11:03:55 -05:00
renovate-bot added 1 commit 2026-01-24 11:03:56 -05:00
🔧 Renovate: Update (minor) actions/setup-node action to v2.5.2 562cc9a87c
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 562cc9a87c to c1fcc375df 2026-01-24 11:19:46 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from c1fcc375df to 416d00892d 2026-01-24 11:43:55 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 416d00892d to e0caeb0708 2026-01-24 13:38:54 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from e0caeb0708 to 896ba6bdd4 2026-01-25 00:21:13 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 896ba6bdd4 to a2d891fcad 2026-01-25 02:14:08 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from a2d891fcad to fb4bd7b5ca 2026-01-26 17:11:58 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from fb4bd7b5ca to 4d686caf98 2026-01-26 19:41:11 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 4d686caf98 to 6fb4fd4085 2026-01-26 20:12:43 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 6fb4fd4085 to 8a88bb4066 2026-01-30 17:30:31 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 8a88bb4066 to 0dc57c1e45 2026-02-01 02:43:38 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 0dc57c1e45 to fb971e327b 2026-02-01 14:19:50 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from fb971e327b to 365a2028f6 2026-02-01 19:42:10 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 365a2028f6 to 06c4bd274d 2026-02-02 09:41:23 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 06c4bd274d to 2e4f9d5cc1 2026-02-02 17:08:30 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 2e4f9d5cc1 to 4b5ad9a8f6 2026-02-05 17:20:26 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 4b5ad9a8f6 to 5bdce7e746 2026-02-05 23:34:40 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from 5bdce7e746 to a4779a1cf9 2026-02-08 00:24:22 -05:00 Compare
renovate-bot force-pushed renovate/github-actions-actions-setup-node-v2-5-2 from a4779a1cf9 to ae4ec1b806 2026-02-08 02:51:15 -05:00 Compare
renovate-bot closed this pull request 2026-02-09 14:43:18 -05:00
renovate-bot deleted branch renovate/github-actions-actions-setup-node-v2-5-2 2026-02-09 14:43:20 -05:00
renovate-bot commented 2026-02-09 14:46:18 -05:00
Author
Member
Copy Link
Copy Source

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v2.5.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update (`v2.5.2`). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
Some checks are pending
Gitea Branch PR & Docker Deployment / Check and Create PR (push) Successful in 2m24s
Details
Gitea Branch PR & Docker Deployment / Generate list of added/modified/deleted services (push) Successful in 24s
Details
Gitea Branch PR & Docker Deployment / Docker Compose Dry Run (push) Failing after 6m39s
Details
Gitea Branch PR & Docker Deployment / PR Merge (push) Has been skipped
Details
Gitea Branch PR & Docker Deployment / Docker Compose Deployment (push) Has been skipped
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
dependencies
docker-compose
manual
renovate
No Label dependencies renovate
Milestone
No items
No Milestone
Assignees
Clear assignees
gitea-sonarqube-bot renovate-bot root Trez.One
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Trez/ultima-ai#101
Delete Branch "renovate/github-actions-actions-setup-node-v2-5-2"

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?