Skip to content

chore(deps): lock file maintenance - #98

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

chore(deps): lock file maintenance#98
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-only refresh, no manifest ranges changed (Cargo.toml / package.json untouched), so every bump here is already within previously-accepted semver constraints.

Rust: mostly patch bumps (syn 3.0.4→3.0.5, crossbeam-*, indexmap 2.14.1→2.14.2, wasm-bindgen family, tokio-rustls, cc). The one that looks like a jump, libsqlite3-sys 0.30.1→0.37.0, is pulled in transitively — grepped the repo and found no direct rusqlite/libsqlite3-sys dependency or usage in source, so nothing here to break. plist now also pulls quick-xml 0.42.0 alongside the repo's own direct pin of quick-xml = "0.41" in api/Cargo.toml; two coexisting major versions is normal in Rust's dependency graph and doesn't affect the WebDAV XML code that uses 0.41.

JS: patch/minor bumps to @inquirer/*, hono, jose, postcss, browserslist, etc. — all tooling/transitive deps of Angular build and the MCP SDK, nothing in application code depends on these directly.

CI: chart, release-tag resolution, conventional-commit and sign-off all passed; build/compose/Coverage were still running at review time with nothing failed so far.

No blocking findings.

@github-actions

github-actions Bot commented Sep 7, 2026

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

@ferrlabs-renovate
ferrlabs-renovate Bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from ae30cd5 to 219ae39 Compare September 7, 2026 21:35
Signed-off-by: ferrlabs-renovate[bot] <282300760+ferrlabs-renovate[bot]@users.noreply.github.com>
@ferrlabs-renovate
ferrlabs-renovate Bot force-pushed the renovate/lock-file-maintenance branch from 219ae39 to 7fd0b28 Compare September 8, 2026 04:14
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