Skip to content

chore(deps): lock file maintenance#499

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/lock-file-maintenance
Closed

chore(deps): lock file maintenance#499
renovate[bot] wants to merge 1 commit intomainfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 2, 2026

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 4am on monday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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 renovate bot added the dependencies Renovatebot and dependabot updates label Mar 2, 2026
@renovate renovate bot enabled auto-merge (squash) March 2, 2026 02:05
@github-actions
Copy link

github-actions bot commented Mar 2, 2026

Open in Overmind ↗


model|risks_v6
✨Encryption Key State Risk ✨KMS Key Creation

🔴 Change Signals

Policies 🔴 ▃▂▁ Multiple storage resources experiencing missing encryption and missing required metadata (10 findings), plus network access resources allowing SSH (port 22) from anywhere (0.0.0.0/0) (2 findings), which is unusual compared to typical patterns and may need review.

View signals ↗


🔥 Risks

Note

No changes in plan

Terraform reported no resources to create, update, or delete.



💥 Blast Radius

Items 0

Edges 0

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overmind

⛔ Auto-Blocked


🔴 Decision

Auto-blocked: Routine score (-5) is below minimum (-1)


📊 Signals Summary

Routine 🔴 -5


🔥 Risks Summary

High 0 · Medium 0 · Low 0


💥 Blast Radius

Items 1 · Edges 0


View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from d035243 to 197daa0 Compare March 5, 2026 17:41
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overmind

⛔ Auto-Blocked


🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)


📊 Signals Summary

Policies 🔴 -3


🔥 Risks Summary

High 0 · Medium 0 · Low 0


View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 197daa0 to 56754e1 Compare March 13, 2026 16:48
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overmind

⛔ Auto-Blocked


🔴 Decision

Auto-blocked: Policy signal (-3) is below threshold (-2)


📊 Signals Summary

Policies 🔴 -3


🔥 Risks Summary

High 0 · Medium 0 · Low 0


View full analysis in Overmind ↗

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from dd150a3 to 5a27663 Compare March 24, 2026 22:29
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 5a27663 to 70f1628 Compare March 24, 2026 22:36
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 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: modules/api-server/demo-app/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 unable to resolve dependency tree
npm error
npm error While resolving: vite_react_shadcn_ts@0.0.0
npm error Found: eslint@10.1.0
npm error node_modules/eslint
npm error   dev eslint@"^10.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0 || ^9.0.0" from eslint-plugin-react-hooks@7.0.1
npm error node_modules/eslint-plugin-react-hooks
npm error   dev eslint-plugin-react-hooks@"^7.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-03-24T22_36_06_444Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-24T22_36_06_444Z-debug-0.log

@dylanratcliffe
Copy link
Member

Retrigger: the .npmrc with legacy-peer-deps=true has been merged to main (#509), so the artifact failure should be resolved on the next rebase.

dylanratcliffe added a commit that referenced this pull request Mar 24, 2026
Regenerated package-lock.json with latest resolved versions.
Supersedes #499.

Made-with: Cursor
@dylanratcliffe
Copy link
Member

Superseded by #510 which refreshed the lock file successfully. The underlying artifact failure was fixed by #509 (added .npmrc with legacy-peer-deps).

auto-merge was automatically disabled March 24, 2026 22:48

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Renovatebot and dependabot updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant