deps: Lock file maintenance - #23
Conversation
9c51204 to
f4f1966
Compare
There was a problem hiding this comment.
💡 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".
| "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", |
There was a problem hiding this comment.
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 👍 / 👎.
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: (in timezone UTC)
* 0-3 * * 1)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.