Skip to content

chore(deps): lock file maintenance#117

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Feb 16, 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 - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

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

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 force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from a486467 to 1c9728f Compare March 10, 2026 23:49
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 1c9728f to a147619 Compare March 13, 2026 14:28
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from ebf49c9 to 7caa3ce Compare March 30, 2026 23:50
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 7caa3ce to f58a6ea Compare April 1, 2026 04:39
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Apr 1, 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: 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 warn Unknown project config "shamefully-hoist". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency

<--- Last few GCs --->

[1409:0x4336e000]   481898 ms: Mark-Compact 1565.7 (1603.4) -> 1314.9 (1398.3) MB, pooled: 0 MB, 391.37 / 0.00 ms  (average mu = 0.343, current mu = 0.343) allocation failure; scavenge might not succeed
[1409:0x4336e000]   482461 ms: Mark-Compact 1485.7 (1569.1) -> 1314.9 (1462.0) MB, pooled: 0 MB, 359.09 / 0.00 ms  (average mu = 0.353, current mu = 0.362) allocation failure; scavenge might not succeed

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x735eec node::OOMErrorHandler(char const*, v8::OOMDetails const&) [npm install]
 2: 0xbafbd0  [npm install]
 3: 0xbafcbf  [npm install]
 4: 0xe49875  [npm install]
 5: 0xe498a2  [npm install]
 6: 0xe49b9a  [npm install]
 7: 0xe5a89a  [npm install]
 8: 0xe5ec40  [npm install]
 9: 0x18f3681  [npm install]
/usr/local/bin/node: line 18:  1409 Aborted                 /opt/containerbase/tools/node/24.14.1/bin/node "$@"

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants