Skip to content

chore(deps): update node dependencies#151

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/node
Closed

chore(deps): update node dependencies#151
renovate[bot] wants to merge 1 commit intomainfrom
renovate/node

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Feb 16, 2026

This PR contains the following updates:

Package Change Age Confidence Type Update
@swc/cli ^0.7.0^0.8.0 age confidence devDependencies minor
node (source) 24.13.024.13.1 age confidence volta patch

Release Notes

nodejs/node (node)

v24.13.1

Compare Source


Configuration

📅 Schedule: Branch creation - "before 6am every weekday" in timezone America/Vancouver, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Feb 16, 2026

⚠️ 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: backend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/cli@11.0.14
npm error Found: @swc/cli@0.8.0
npm error node_modules/@swc/cli
npm error   dev @swc/cli@"^0.8.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @swc/cli@"^0.1.62 || ^0.3.0 || ^0.4.0 || ^0.5.0 || ^0.6.0 || ^0.7.0" from @nestjs/cli@11.0.14
npm error node_modules/@nestjs/cli
npm error   @nestjs/cli@"^11.0.0" from the root project
npm error
npm error Conflicting peer dependency: @swc/cli@0.7.10
npm error node_modules/@swc/cli
npm error   peerOptional @swc/cli@"^0.1.62 || ^0.3.0 || ^0.4.0 || ^0.5.0 || ^0.6.0 || ^0.7.0" from @nestjs/cli@11.0.14
npm error   node_modules/@nestjs/cli
npm error     @nestjs/cli@"^11.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-19T17_33_23_388Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-19T17_33_23_388Z-debug-0.log

@DerekRoberts
Copy link
Copy Markdown
Member

https://gh.io/copilot-coding-agent-docs Can you handle these dependency updates? Please feel free to update only one or update unmentioned codependencies to achieve our desired outcome, which is up-to-date patch dependencies. Relay your outcomes and concerns in the resulting PR.

A nearly identical PR from @copilot is here. bcgov/quickstart-aws-sql#257

Copy link
Copy Markdown

Copilot AI commented Feb 16, 2026

@DerekRoberts I've opened a new pull request, #152, to work on those changes. Once the pull request is ready, I'll request review from you.

@DerekRoberts
Copy link
Copy Markdown
Member

Node handled in #154. swc not ready.

auto-merge was automatically disabled February 19, 2026 17:36

Pull request was closed

@github-project-automation github-project-automation bot moved this from Waiting to Done in NRIDS - Architecture Feb 19, 2026
@DerekRoberts DerekRoberts deleted the renovate/node branch February 19, 2026 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants