Skip to content

chore(deps): lock file maintenance - #802

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Jun 29, 2026 •

Copy link
Copy Markdown
Contributor

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: (UTC)

  • Branch creation
    • "before 4am on monday"
  • 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 renovate Bot added the dependencies Pull requests that update a dependency file label Jun 29, 2026
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from e213fa1 to b8ef17c Compare July 17, 2026 13:47
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 61403a0 to b8e7144 Compare July 24, 2026 20:46
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from ce01c1a to aeecab9 Compare July 31, 2026 04:30
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from d3019ef to a34008d Compare August 16, 2026 10:36
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from a34008d to a0d5761 Compare August 26, 2026 13:56
@renovate
renovate Bot requested a review from a team August 26, 2026 13:56
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 7 times, most recently from 5bd9c67 to c2d6de7 Compare September 9, 2026 18:47
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from c2d6de7 to 40290ed Compare September 10, 2026 21:16
@coderabbitai

coderabbitai Bot commented Sep 10, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 9a64d241-18de-4323-9ffa-4f0d78e24b67

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 74bc2c0 to c82cd4e Compare September 11, 2026 12:28
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 2c63491 to 98a0e63 Compare September 16, 2026 10:29
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 29475ee to 01dec06 Compare October 1, 2026 00:05
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from db45a10 to fe0253a Compare October 5, 2026 13:36
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from fe0253a to cff7d98 Compare October 10, 2026 07:11
@renovate renovate Bot changed the title Lock file maintenance chore(deps): lock file maintenance Oct 10, 2026
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from efc2c15 to 7e4db31 Compare October 20, 2026 11:02
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 638cf47 to 1ec6917 Compare October 26, 2026 16:48
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 5d5daf9 to eb7eeb8 Compare November 5, 2026 22:36
@renovate

renovate Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ 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: frontend-nextjs/package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EALLOWREMOTE
npm error Fetching packages of type "remote" have been disabled
npm error Refusing to fetch "https://registry.npmjs.org/@tailwindcss/oxide-wasm32-wasi/-/oxide-wasm32-wasi-4.3.5.tgz"
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-20T17_45_56_848Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from d4291fd to 38fd673 Compare November 16, 2026 23:42
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 38fd673 to 4a40651 Compare November 20, 2026 17:46

This branch has not been deployed

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants