Skip to content

chore(deps): lock file maintenance - #9

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

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

Conversation

@ferrlabs-renovate

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 6am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@ferrfleet ferrfleet 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.

Lock file maintenance only, no Cargo.toml changes. Six transitive crates bumped, all patch/minor within existing semver ranges: bitflags 2.13.1→2.13.2, cc 1.4.5→1.4.6, lru-slab 0.1.2→0.1.3, rustls 0.23.43→0.23.44, smallvec 1.16.0→1.16.1, and tinyvec 1.13.2→1.13.3 (which absorbed tinyvec_macros as an internal dep, removing that separate lock entry). No API surface in this repo touches these directly beyond normal usage through their public dependents, and patch-level bumps in these crates are bugfix/security releases, not behavior changes.

Checks were still in progress/queued at review time (Image builds, Action manifest, Check) — nothing failed, just not finished yet.

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