Configure Renovate

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

---

Detected Package Files

• .github/workflows/Comment_command.yml (github-actions)
• .github/workflows/Relabel_issue.yml (github-actions)
• .github/workflows/_codeql.yml (github-actions)
• .github/workflows/_common-lint.yml (github-actions)
• .github/workflows/auto-update-db.yml (github-actions)
• .github/workflows/python-tests.yml (github-actions)
• .github/workflows/update-pages.yml (github-actions)
• package.json (npm)
• requirements-dev.txt (pip_requirements)
• requirements.txt (pip_requirements)
• renovate.json (renovate-config-presets)

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
• Use curated list of recommended non-monorepo package groupings.
• Default renovate configuration for LizardByte repositories
• Renovate onboarding preset for use with LizardByte's repos
• Run Renovate on following schedule: after 1am,before 6am

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

---

What to Expect

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

fix(deps): bump dependency electron to v35 [security]

• Branch name: renovate/npm-electron-vulnerability
• Merge into: master
• Upgrade electron to 35.7.5

chore(deps): bump dependency psutil to v6.1.1

• Schedule: ["after 1am","before 6am"]
• Branch name: renovate/psutil-6-x
• Merge into: master
• Upgrade psutil to ==6.1.1

chore(deps): bump dependency plotly to v6

• Schedule: ["after 1am","before 6am"]
• Branch name: renovate/plotly-6-x
• Merge into: master
• Upgrade plotly to ==6.5.0

chore(deps): bump dependency psutil to v7

• Schedule: ["after 1am","before 6am"]
• Branch name: renovate/psutil-7-x
• Merge into: master
• Upgrade psutil to ==7.1.3

🚸 Branch 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.98%. Comparing base (ceab515) to head (4f1e759).
⚠️ Report is 121 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1819   +/-   ##
=======================================
  Coverage   85.98%   85.98%           
=======================================
  Files           1        1           
  Lines         314      314           
=======================================
  Hits          270      270           
  Misses         44       44           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[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 SonarCloud