chore(deps): update dependency @types/node to v24 #272

Closed
b4mad-renovate wants to merge 1 commit from refs/pull/272/head into main
b4mad-renovate commented 2025-10-28 00:12:43 +00:00 (Migrated from codeberg.org)

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) ^22.0.0^24.0.0 age confidence

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Every minute (* * * * *)

🚦 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 Mend Renovate.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | [`^22.0.0` → `^24.0.0`](https://renovatebot.com/diffs/npm/@types%2fnode/22.13.10/24.12.3) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2fnode/24.12.3?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2fnode/22.13.10/24.12.3?slim=true) | --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - Every minute (`* * * * *`) 🚦 **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 [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTUuNSIsInVwZGF0ZWRJblZlciI6IjQzLjE2OC42IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
b4mad-renovate commented 2025-10-28 00:12:44 +00:00 (Migrated from codeberg.org)

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: feeldata.app@0.10.2
npm error Found: @storybook/addon-a11y@9.2.0-alpha.1
npm error node_modules/@storybook/addon-a11y
npm error   dev @storybook/addon-a11y@"^10.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @storybook/addon-a11y@"^10.0.0" from the root project
npm error
npm error Conflicting peer dependency: storybook@10.3.6
npm error node_modules/storybook
npm error   peer storybook@"^10.3.6" from @storybook/addon-a11y@10.3.6
npm error   node_modules/@storybook/addon-a11y
npm error     dev @storybook/addon-a11y@"^10.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-05-12T07_09_36_437Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-12T07_09_36_437Z-debug-0.log

### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: package-lock.json ``` npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: feeldata.app@0.10.2 npm error Found: @storybook/addon-a11y@9.2.0-alpha.1 npm error node_modules/@storybook/addon-a11y npm error dev @storybook/addon-a11y@"^10.0.0" from the root project npm error npm error Could not resolve dependency: npm error dev @storybook/addon-a11y@"^10.0.0" from the root project npm error npm error Conflicting peer dependency: storybook@10.3.6 npm error node_modules/storybook npm error peer storybook@"^10.3.6" from @storybook/addon-a11y@10.3.6 npm error node_modules/@storybook/addon-a11y npm error dev @storybook/addon-a11y@"^10.0.0" from the root project npm error npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /tmp/renovate/cache/others/npm/_logs/2026-05-12T07_09_36_437Z-eresolve-report.txt npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-12T07_09_36_437Z-debug-0.log ```
op1st-gitops commented 2025-10-28 00:12:46 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-k52zl is running.

Starting Pipelinerun on-pull-request-k52zl in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-k52zl -f

op1st Pipelines as Code/on-pull-request-k52zl is running. Starting Pipelinerun <b>on-pull-request-k52zl</b> in namespace<b> feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-k52zl) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-k52zl -f</code>
op1st-gitops commented 2025-10-28 00:14:56 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-k52zl has successfully validated your commit.


Task Statuses:

StatusDurationName
Succeeded 12 seconds

fetch-source-repository

Succeeded 1 minute

unit-tests

op1st Pipelines as Code/on-pull-request-k52zl has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">feeldata-dev</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-k52zl">on-pull-request-k52zl</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>12 seconds</td><td> [fetch-source-repository](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-k52zl/logs/fetch-source-repository) </td></tr> <tr> <td>Succeeded</td> <td>1 minute</td><td> [unit-tests](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-k52zl/logs/unit-tests) </td></tr> </table>
op1st-gitops commented 2025-11-21 06:56:28 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-jw2ml is running.

Starting Pipelinerun on-pull-request-jw2ml in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-jw2ml -f

op1st Pipelines as Code/on-pull-request-jw2ml is running. Starting Pipelinerun <b>[on-pull-request-jw2ml](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-jw2ml)</b> in namespace <b>feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-jw2ml) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-jw2ml -f</code>
op1st-gitops commented 2025-11-21 07:22:57 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-cz7sd is running.

Starting Pipelinerun on-pull-request-cz7sd in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-cz7sd -f

op1st Pipelines as Code/on-pull-request-cz7sd is running. Starting Pipelinerun <b>[on-pull-request-cz7sd](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-cz7sd)</b> in namespace <b>feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-cz7sd) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-cz7sd -f</code>
op1st-gitops commented 2025-11-21 07:38:16 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-t7x4k is running.

Starting Pipelinerun on-pull-request-t7x4k in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-t7x4k -f

op1st Pipelines as Code/on-pull-request-t7x4k is running. Starting Pipelinerun <b>[on-pull-request-t7x4k](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-t7x4k)</b> in namespace <b>feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-t7x4k) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-t7x4k -f</code>
op1st-gitops commented 2025-11-28 07:06:53 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-h65ks is running.

Starting Pipelinerun on-pull-request-h65ks in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-h65ks -f

op1st Pipelines as Code/on-pull-request-h65ks is running. Starting Pipelinerun <b>[on-pull-request-h65ks](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-h65ks)</b> in namespace <b>feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-h65ks) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-h65ks -f</code>
op1st-gitops commented 2026-01-01 05:05:06 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-6nwh7 is running.

Starting Pipelinerun on-pull-request-6nwh7 in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-6nwh7 -f

op1st Pipelines as Code/on-pull-request-6nwh7 is running. Starting Pipelinerun <b>[on-pull-request-6nwh7](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-6nwh7)</b> in namespace <b>feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-6nwh7) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-6nwh7 -f</code>
op1st-gitops commented 2026-01-01 05:05:44 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-6nwh7 has failed.


Task Statuses:

StatusDurationName
Succeeded 10 seconds

fetch-source-repository

Failed 24 seconds

unit-tests


Failure snippet:

task unit-tests has the status "Failed":
> jest -c jest.config.d/units.ts --randomize --rootDir=. --coverage --verbose

sh: line 1: jest: command not found

op1st Pipelines as Code/on-pull-request-6nwh7 has <b>failed</b>. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">feeldata-dev</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-6nwh7">on-pull-request-6nwh7</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>10 seconds</td><td> [fetch-source-repository](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-6nwh7/logs/fetch-source-repository) </td></tr> <tr> <td>Failed</td> <td>24 seconds</td><td> [unit-tests](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-6nwh7/logs/unit-tests) </td></tr> </table> <hr> <h4>Failure snippet:</h4> task <b>unit-tests</b> has the status <b>"Failed"</b>: <pre>> jest -c jest.config.d/units.ts --randomize --rootDir=. --coverage --verbose sh: line 1: jest: command not found</pre>
op1st-gitops commented 2026-01-04 19:05:09 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-z2xhh is running.

Starting Pipelinerun on-pull-request-z2xhh in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-z2xhh -f

op1st Pipelines as Code/on-pull-request-z2xhh is running. Starting Pipelinerun <b>[on-pull-request-z2xhh](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-z2xhh)</b> in namespace <b>feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-z2xhh) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-z2xhh -f</code>
op1st-gitops commented 2026-01-04 19:05:41 +00:00 (Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-z2xhh has failed.


Task Statuses:

StatusDurationName
Succeeded 9 seconds

fetch-source-repository

Failed 22 seconds

unit-tests


Failure snippet:

task unit-tests has the status "Failed":
> jest -c jest.config.d/units.ts --randomize --rootDir=. --coverage --verbose

sh: line 1: jest: command not found

op1st Pipelines as Code/on-pull-request-z2xhh has <b>failed</b>. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">feeldata-dev</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-z2xhh">on-pull-request-z2xhh</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>9 seconds</td><td> [fetch-source-repository](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-z2xhh/logs/fetch-source-repository) </td></tr> <tr> <td>Failed</td> <td>22 seconds</td><td> [unit-tests](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-z2xhh/logs/unit-tests) </td></tr> </table> <hr> <h4>Failure snippet:</h4> task <b>unit-tests</b> has the status <b>"Failed"</b>: <pre>> jest -c jest.config.d/units.ts --randomize --rootDir=. --coverage --verbose sh: line 1: jest: command not found</pre>
b4mad-renovate commented 2026-05-12 08:14:39 +00:00 (Migrated from codeberg.org)

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 24.x releases. But if you manually upgrade to 24.x then Renovate will re-enable minor and patch updates automatically.

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. You will not get PRs for *any* future `24.x` releases. But if you manually upgrade to `24.x` then Renovate will re-enable `minor` and `patch` updates automatically. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
feeldata/feeldata.app!272
No description provided.