build: Configure Renovate - autoclosed

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

Detected Package Files

• Cargo.toml (cargo)
• crates/server/Cargo.toml (cargo)
• .github/workflows/_codeql.yml (github-actions)
• .github/workflows/_common-lint.yml (github-actions)
• .github/workflows/_top-issues.yml (github-actions)
• .github/workflows/ci.yml (github-actions)
• renovate.json (renovate-config-presets)
• rust-toolchain.toml (regex)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Use curated list of recommended non-monorepo package groupings.
• Use semantic prefixes for commit messages and PR titles.
• If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
• Default renovate configuration for LizardByte repositories
• Renovate onboarding preset for use with LizardByte's repos
• Run Renovate on following schedule: after 1am,before 8am

---

What to Expect

With your current configuration, Renovate will create 9 Pull Requests:

chore(deps): update rust crate jsonwebtoken to v10 [security]

• Branch name: renovate/crate-jsonwebtoken-vulnerability
• Merge into: master
• Upgrade jsonwebtoken to 10.3.0

chore(deps): update rust crate bcrypt to 0.19.0

• Schedule: ["after 1am","before 8am"]
• Branch name: renovate/bcrypt-0-x
• Merge into: master
• Upgrade bcrypt to 0.19.0

chore(deps): update rust crate libsqlite3-sys to 0.37

• Schedule: ["after 1am","before 8am"]
• Branch name: renovate/libsqlite3-sys-0-x
• Merge into: master
• Upgrade libsqlite3-sys to 0.37

chore(deps): update rust crate rand to 0.10.0

• Schedule: ["after 1am","before 8am"]
• Branch name: renovate/rand-0-x
• Merge into: master
• Upgrade rand to 0.10.0

chore(deps): update rust crate rcgen to 0.14.0

• Schedule: ["after 1am","before 8am"]
• Branch name: renovate/rcgen-0-x
• Merge into: master
• Upgrade rcgen to 0.14.0

chore(deps): update rust crate rstest to 0.26.0

• Schedule: ["after 1am","before 8am"]
• Branch name: renovate/rstest-0-x
• Merge into: master
• Upgrade rstest to 0.26.0

chore(deps): update rust crate schemars to 0.9.0

• Schedule: ["after 1am","before 8am"]
• Branch name: renovate/schemars-0-x
• Merge into: master
• Upgrade schemars to 0.9.0

chore(deps): update rust crate tao to 0.35.0

• Schedule: ["after 1am","before 8am"]
• Branch name: renovate/tao-0-x
• Merge into: master
• Upgrade tao to 0.35.0

chore(deps): update rust crate schemars to v1

• Schedule: ["after 1am","before 8am"]
• Branch name: renovate/schemars-1-x
• Merge into: master
• Upgrade schemars to 1.0.0

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.97%. Comparing base (36429eb) to head (199cfaf).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #91      +/-   ##
==========================================
- Coverage   72.16%   71.97%   -0.19%     
==========================================
  Files          15       15              
  Lines         546      546              
==========================================
- Hits          394      393       -1     
- Misses        152      153       +1     

Flag	Coverage Δ
aarch64-apple-darwin	50.27% <ø> (+1.65%)	⬆️
aarch64-unknown-linux-gnu	71.97% <ø> (ø)
x86_64-apple-darwin	48.61% <ø> (-23.95%)	⬇️
x86_64-pc-windows-msvc	71.97% <ø> (ø)
x86_64-unknown-linux-gnu	71.97% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 36429eb...199cfaf. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud