chore(deps): lock file maintenance - #118
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/lock-file-maintenance
branch
14 times, most recently
from
July 28, 2026 13:52
1d3f2f2 to
3c4a385
Compare
renovate
Bot
force-pushed
the
renovate/lock-file-maintenance
branch
4 times, most recently
from
July 30, 2026 15:12
acd625a to
a205983
Compare
renovate
Bot
force-pushed
the
renovate/lock-file-maintenance
branch
6 times, most recently
from
August 16, 2026 19:57
12aad6a to
968caf0
Compare
roschaefer
added a commit
that referenced
this pull request
Aug 23, 2026
Codex flagged that this branch's lockfile still resolved biome 2.5.5 while biome.json's schema now pins 2.5.8 - the branch never included the actual lock-file-maintenance bump, just a schema change written against it. Rebuilt on top of that lockfile bump (#118) so the resolved version and schema agree, and pinned the range exactly so future lockFileMaintenance runs can't drift the resolved version past the schema again (see the matching renovate.json change).
roschaefer
added a commit
that referenced
this pull request
Aug 23, 2026
…133) …of schema lockFileMaintenance re-resolves the lockfile to the newest version allowed by package.json's semver range, but it doesn't run the customManagers step that keeps biome.json's $schema pin in sync. That let @biomejs/biome drift to 2.5.8 in pnpm-lock.yaml while biome.json still declared 2.5.5, which biome treats as a hard error (#118). Excluding @biomejs/biome from lockFileMaintenance means its resolved version can only change via the dedicated "update dependency @biomejs/biome" PR, which updates biome.json in the same commit.
roschaefer
added a commit
that referenced
this pull request
Aug 23, 2026
Codex flagged that this branch's lockfile still resolved biome 2.5.5 while biome.json's schema now pins 2.5.8 - the branch never included the actual lock-file-maintenance bump, just a schema change written against it. Rebuilt on top of that lockfile bump (#118) so the resolved version and schema agree, and pinned the range exactly so future lockFileMaintenance runs can't drift the resolved version past the schema again (see the matching renovate.json change).
renovate
Bot
force-pushed
the
renovate/lock-file-maintenance
branch
from
August 23, 2026 21:56
968caf0 to
1f607fe
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.