Skip to content

chore(deps): lock file maintenance - #269

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 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 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, three patch bumps: cc 1.4.6→1.4.7, find-msvc-tools 0.1.12→0.1.13, hyper-rustls 0.27.9→0.27.10. All patch-level within existing semver ranges, no manifest changes. cc and find-msvc-tools are build-time-only dependencies (MSVC toolchain detection for C compilation); hyper-rustls patch releases are routine fixes and don't change the TLS API surface this repo would call. Nothing here touches breaking changes or removed APIs.

CI: most checks (zizmor, gitleaks, osv-scanner, snyk, PR title) passed; Test/Lint/Security/RUSTSEC audit/kind smoke test were still in progress at review time with nothing failed so far. Nothing in this diff suggests a build or test failure is coming from it.

No blocking findings.

@github-actions

Copy link
Copy Markdown

SonarQube — aucune nouvelle issue

Comparaison entre le projet bac à sable de cette PR et la branche par défaut : SonarQube Community n'analyse pas les PR, ce delta est calculé côté CI. Détail

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