Skip to content

deps: Lock file maintenance - #23

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/lock-file-maintenance
Aug 3, 2026
Merged

deps: Lock file maintenance#23
renovate[bot] merged 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Aug 3, 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: (in timezone UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • 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 label Aug 3, 2026
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 9c51204 to f4f1966 Compare August 3, 2026 06:58

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f4f1966cfc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread package-lock.json
"version": "6.2.4",
"resolved": "https://registry.npmjs.org/jose/-/jose-6.2.4.tgz",
"integrity": "sha512-N8acGzVsQy6M/fjFcxtysNc4Q379TcM5dM/qKkNtsHFji88yANnXTr7BLeP75iPnFwBfQzM/jg2BZ9+HZrHCZA==",
"version": "6.2.7",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Refresh bun.lock alongside package-lock

The root package declares packageManager: bun@1.3.13 and this repo has a checked-in bun.lock, but this lockfile maintenance only updates package-lock.json; bun pm ls --all (Bun help: “according to the current lockfile”) still resolves jose@6.2.4 from bun.lock:356 while this line pins 6.2.7 (similarly hono remains 4.12.32). In any Bun/frozen-lockfile install the dependency graph stays on the old versions, so the refresh is not reproducible across the repo’s declared package manager; refresh bun.lock with the same dependency updates.

Useful? React with 👍 / 👎.

@renovate
renovate Bot merged commit 1f7b948 into main Aug 3, 2026
2 checks passed
@renovate
renovate Bot deleted the renovate/lock-file-maintenance branch August 3, 2026 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants