ai/panelist
3
Fork 0
Code Issues Pull requests 1 Projects Releases Packages 1 Activity Actions

chore: Configure Renovate #1

Open
renovate-bot wants to merge 1 commit from renovate/configure into main
pull from: renovate/configure
merge into: ai:main
Conversation 0 Commits 1 Files changed 1 +6
renovate-bot commented 2026-05-06 21:41:32 +02:00
Member
Copy link

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)
  • panelist-core/Cargo.toml (cargo)
  • panelist-e2e/Cargo.toml (cargo)
  • panelist/Cargo.toml (cargo)
  • deploy/docker-compose/docker-compose.yml (docker-compose)
  • Dockerfile.ci-builder (dockerfile)
  • Dockerfile.runtime (dockerfile)
  • .gitlab-ci.yml (gitlabci)
  • deploy/kubernetes/kustomization.yaml (kustomize)
  • renovate.json (renovate-config)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • 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 Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.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
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for development dependencies.
  • Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  • Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
  • Run lock file maintenance (updates) early Monday mornings.
  • Remove hourly and concurrent rate limits.

What to Expect

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

chore(deps): pin dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:6967db29ce5294d054121e94b3cb1262de858af63b4547bb1bade66a4306f2e4
  • Pin base64 to =0.22.1
  • Upgrade debian to sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb
  • Pin dioxus-ssr to =0.7.6
  • Upgrade moby/buildkit to sha256:d76eb1caecac5733ef7553c1e90a1b21f1bb218cd1142d3553de0747b4a14ba9
  • Pin reqwest to =0.12.28
  • Upgrade rust to sha256:6258907abe69656e41cd992e0b705cdcfabcbbe3db374f92ed2d47121282d4a1
  • Pin uuid to =1.23.1
chore(deps): update aquasec/trivy docker tag to v0.61.1
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.61.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:91bcccab7cb503127b0d792db7c652c4e556c9ff30eeb0908b6ae1980d7727ad
chore(deps): update rust crate dioxus to v0.7.9
  • Schedule: ["at any time"]
  • Branch name: renovate/dioxus-0.7.x-lockfile
  • Merge into: main
  • Upgrade dioxus to 0.7.9
chore(deps): update rust crate tokio to v1.52.3
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-1.52.x-lockfile
  • Merge into: main
  • Upgrade tokio to 1.52.3
chore(deps): update rust crate tower-http to v0.6.11
  • Schedule: ["at any time"]
  • Branch name: renovate/tower-http-0.6.x-lockfile
  • Merge into: main
  • Upgrade tower-http to 0.6.11
chore(deps): update rust-wasm-bindgen monorepo (patch)
  • Schedule: ["at any time"]
  • Branch name: renovate/patch-rust-wasm-bindgen-monorepo
  • Merge into: main
  • Upgrade js-sys to 0.3.98
  • Upgrade wasm-bindgen to 0.2.121
  • Upgrade web-sys to 0.3.98
chore(deps): update aquasec/trivy docker tag to v0.62.1
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.62.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:fc10faf341a1d8fa8256c5ff1a6662ef74dd38b65034c8ce42346cf958a02d5d
chore(deps): update aquasec/trivy docker tag to v0.63.0
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.63.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:6fb0646988fcd2fdf7bf123f7174945ebc2c9c72d1fa1567c8d7daeeb70f8037
chore(deps): update aquasec/trivy docker tag to v0.64.1
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.64.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:a8ca29078522f30393bdb34225e4c0994d38f37083be81a42da3a2a7e1488e9e
chore(deps): update aquasec/trivy docker tag to v0.65.0
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.65.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:a22415a38938a56c379387a8163fcb0ce38b10ace73e593475d3658d578b2436
chore(deps): update aquasec/trivy docker tag to v0.66.0
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.66.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:086971aaf400beebd94e8300fd8ea623774419597169156cec56eec5b00dfb1e
chore(deps): update aquasec/trivy docker tag to v0.67.2
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.67.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:e2b22eac59c02003d8749f5b8d9bd073b62e30fefaef5b7c8371204e0a4b0c08
chore(deps): update aquasec/trivy docker tag to v0.68.2
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.68.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:05d0126976bdedcd0782a0336f77832dbea1c81b9cc5e4b3a5ea5d2ec863aca7
chore(deps): update aquasec/trivy docker tag to v0.69.3
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.69.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:bcc376de8d77cfe086a917230e818dc9f8528e3c852f7b1aff648949b6258d1c
chore(deps): update aquasec/trivy docker tag to v0.70.0
  • Schedule: ["at any time"]
  • Branch name: renovate/aquasec-trivy-0.70.x
  • Merge into: main
  • Upgrade aquasec/trivy to sha256:be1190afcb28352bfddc4ddeb71470835d16462af68d310f9f4bca710961a41e
chore(deps): update rust crate dashmap to v6.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/dashmap-6.2.x-lockfile
  • Merge into: main
  • Upgrade dashmap to 6.2.1
fix(deps): update rust crate chromiumoxide to 0.9
  • Schedule: ["at any time"]
  • Branch name: renovate/chromiumoxide-0.9.x
  • Merge into: main
  • Upgrade chromiumoxide to 0.9
fix(deps): update rust crate gloo-timers to 0.4
  • Schedule: ["at any time"]
  • Branch name: renovate/gloo-timers-0.4.x
  • Merge into: main
  • Upgrade gloo-timers to 0.4
fix(deps): update rust crate lru to 0.17.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lru-0.17.x
  • Merge into: main
  • Upgrade lru to 0.17.0
fix(deps): update rust crate lru to 0.18.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lru-0.18.x
  • Merge into: main
  • Upgrade lru to 0.18.0
fix(deps): update rust crate pulldown-cmark to 0.13
  • Schedule: ["at any time"]
  • Branch name: renovate/pulldown-cmark-0.13.x
  • Merge into: main
  • Upgrade pulldown-cmark to 0.13
fix(deps): update rust crate rand to 0.10.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rand-0.10.x
  • Merge into: main
  • Upgrade rand to 0.10.0
fix(deps): update rust crate reqwest to 0.13
  • Schedule: ["at any time"]
  • Branch name: renovate/reqwest-0.13.x
  • Merge into: main
  • Upgrade reqwest to 0.13
fix(deps): update rust crate rmcp to 0.15
  • Schedule: ["at any time"]
  • Branch name: renovate/rmcp-0.15.x
  • Merge into: main
  • Upgrade rmcp to 0.15
fix(deps): update rust crate rmcp to 0.16
  • Schedule: ["at any time"]
  • Branch name: renovate/rmcp-0.16.x
  • Merge into: main
  • Upgrade rmcp to 0.16
fix(deps): update rust crate rmcp to 0.17
  • Schedule: ["at any time"]
  • Branch name: renovate/rmcp-0.17.x
  • Merge into: main
  • Upgrade rmcp to 0.17
fix(deps): update rust crate sha2 to 0.11.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sha2-0.11.x
  • Merge into: main
  • Upgrade sha2 to 0.11.0
chore(deps): update rust crate jsonwebtoken to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/jsonwebtoken-10.x
  • Merge into: main
  • Upgrade jsonwebtoken to 10
fix(deps): update rust crate rmcp to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/rmcp-1.x
  • Merge into: main
  • Upgrade rmcp to 1.0
chore(deps): lock file maintenance
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

❓ 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 has been generated by Mend Renovate.

Welcome to [Renovate](https://github.com/renovatebot/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](https://docs.renovatebot.com/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) * `panelist-core/Cargo.toml` (cargo) * `panelist-e2e/Cargo.toml` (cargo) * `panelist/Cargo.toml` (cargo) * `deploy/docker-compose/docker-compose.yml` (docker-compose) * `Dockerfile.ci-builder` (dockerfile) * `Dockerfile.runtime` (dockerfile) * `.gitlab-ci.yml` (gitlabci) * `deploy/kubernetes/kustomization.yaml` (kustomize) * `renovate.json` (renovate-config) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - 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 Forgejo contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitLab.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 - Pin Docker digests. - Pin `github-action` digests. - Enable Renovate configuration migration PRs when needed. - Pin dependency versions for development dependencies. - Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides. - Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds. - Run lock file maintenance (updates) early Monday mornings. - Remove hourly and concurrent rate limits. --- ### What to Expect With your current configuration, Renovate will create 30 Pull Requests: <details> <summary>chore(deps): pin dependencies</summary> - Schedule: ["at any time"] - Branch name: `renovate/pin-dependencies` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:6967db29ce5294d054121e94b3cb1262de858af63b4547bb1bade66a4306f2e4` - Pin [base64](https://github.com/marshallpierce/rust-base64) to `=0.22.1` - Upgrade debian to `sha256:0104b334637a5f19aa9c983a91b54c89887c0984081f2068983107a6f6c21eeb` - Pin [dioxus-ssr](https://github.com/DioxusLabs/dioxus) to `=0.7.6` - Upgrade moby/buildkit to `sha256:d76eb1caecac5733ef7553c1e90a1b21f1bb218cd1142d3553de0747b4a14ba9` - Pin [reqwest](https://github.com/seanmonstar/reqwest) to `=0.12.28` - Upgrade rust to `sha256:6258907abe69656e41cd992e0b705cdcfabcbbe3db374f92ed2d47121282d4a1` - Pin [uuid](https://github.com/uuid-rs/uuid) to `=1.23.1` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.61.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.61.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:91bcccab7cb503127b0d792db7c652c4e556c9ff30eeb0908b6ae1980d7727ad` </details> <details> <summary>chore(deps): update rust crate dioxus to v0.7.9</summary> - Schedule: ["at any time"] - Branch name: `renovate/dioxus-0.7.x-lockfile` - Merge into: `main` - Upgrade [dioxus](https://github.com/DioxusLabs/dioxus) to `0.7.9` </details> <details> <summary>chore(deps): update rust crate tokio to v1.52.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/tokio-1.52.x-lockfile` - Merge into: `main` - Upgrade [tokio](https://github.com/tokio-rs/tokio) to `1.52.3` </details> <details> <summary>chore(deps): update rust crate tower-http to v0.6.11</summary> - Schedule: ["at any time"] - Branch name: `renovate/tower-http-0.6.x-lockfile` - Merge into: `main` - Upgrade [tower-http](https://github.com/tower-rs/tower-http) to `0.6.11` </details> <details> <summary>chore(deps): update rust-wasm-bindgen monorepo (patch)</summary> - Schedule: ["at any time"] - Branch name: `renovate/patch-rust-wasm-bindgen-monorepo` - Merge into: `main` - Upgrade [js-sys](https://github.com/wasm-bindgen/wasm-bindgen) to `0.3.98` - Upgrade [wasm-bindgen](https://github.com/wasm-bindgen/wasm-bindgen) to `0.2.121` - Upgrade [web-sys](https://github.com/wasm-bindgen/wasm-bindgen) to `0.3.98` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.62.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.62.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:fc10faf341a1d8fa8256c5ff1a6662ef74dd38b65034c8ce42346cf958a02d5d` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.63.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.63.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:6fb0646988fcd2fdf7bf123f7174945ebc2c9c72d1fa1567c8d7daeeb70f8037` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.64.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.64.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:a8ca29078522f30393bdb34225e4c0994d38f37083be81a42da3a2a7e1488e9e` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.65.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.65.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:a22415a38938a56c379387a8163fcb0ce38b10ace73e593475d3658d578b2436` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.66.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.66.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:086971aaf400beebd94e8300fd8ea623774419597169156cec56eec5b00dfb1e` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.67.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.67.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:e2b22eac59c02003d8749f5b8d9bd073b62e30fefaef5b7c8371204e0a4b0c08` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.68.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.68.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:05d0126976bdedcd0782a0336f77832dbea1c81b9cc5e4b3a5ea5d2ec863aca7` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.69.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.69.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:bcc376de8d77cfe086a917230e818dc9f8528e3c852f7b1aff648949b6258d1c` </details> <details> <summary>chore(deps): update aquasec/trivy docker tag to v0.70.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/aquasec-trivy-0.70.x` - Merge into: `main` - Upgrade [aquasec/trivy](https://github.com/aquasecurity/trivy) to `sha256:be1190afcb28352bfddc4ddeb71470835d16462af68d310f9f4bca710961a41e` </details> <details> <summary>chore(deps): update rust crate dashmap to v6.2.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/dashmap-6.2.x-lockfile` - Merge into: `main` - Upgrade [dashmap](https://github.com/xacrimon/dashmap) to `6.2.1` </details> <details> <summary>fix(deps): update rust crate chromiumoxide to 0.9</summary> - Schedule: ["at any time"] - Branch name: `renovate/chromiumoxide-0.9.x` - Merge into: `main` - Upgrade [chromiumoxide](https://github.com/mattsse/chromiumoxide) to `0.9` </details> <details> <summary>fix(deps): update rust crate gloo-timers to 0.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/gloo-timers-0.4.x` - Merge into: `main` - Upgrade [gloo-timers](https://github.com/rustwasm/gloo) to `0.4` </details> <details> <summary>fix(deps): update rust crate lru to 0.17.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/lru-0.17.x` - Merge into: `main` - Upgrade [lru](https://github.com/jeromefroe/lru-rs) to `0.17.0` </details> <details> <summary>fix(deps): update rust crate lru to 0.18.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/lru-0.18.x` - Merge into: `main` - Upgrade [lru](https://github.com/jeromefroe/lru-rs) to `0.18.0` </details> <details> <summary>fix(deps): update rust crate pulldown-cmark to 0.13</summary> - Schedule: ["at any time"] - Branch name: `renovate/pulldown-cmark-0.13.x` - Merge into: `main` - Upgrade [pulldown-cmark](https://github.com/raphlinus/pulldown-cmark) to `0.13` </details> <details> <summary>fix(deps): update rust crate rand to 0.10.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/rand-0.10.x` - Merge into: `main` - Upgrade [rand](https://github.com/rust-random/rand) to `0.10.0` </details> <details> <summary>fix(deps): update rust crate reqwest to 0.13</summary> - Schedule: ["at any time"] - Branch name: `renovate/reqwest-0.13.x` - Merge into: `main` - Upgrade [reqwest](https://github.com/seanmonstar/reqwest) to `0.13` </details> <details> <summary>fix(deps): update rust crate rmcp to 0.15</summary> - Schedule: ["at any time"] - Branch name: `renovate/rmcp-0.15.x` - Merge into: `main` - Upgrade [rmcp](https://github.com/modelcontextprotocol/rust-sdk) to `0.15` </details> <details> <summary>fix(deps): update rust crate rmcp to 0.16</summary> - Schedule: ["at any time"] - Branch name: `renovate/rmcp-0.16.x` - Merge into: `main` - Upgrade [rmcp](https://github.com/modelcontextprotocol/rust-sdk) to `0.16` </details> <details> <summary>fix(deps): update rust crate rmcp to 0.17</summary> - Schedule: ["at any time"] - Branch name: `renovate/rmcp-0.17.x` - Merge into: `main` - Upgrade [rmcp](https://github.com/modelcontextprotocol/rust-sdk) to `0.17` </details> <details> <summary>fix(deps): update rust crate sha2 to 0.11.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/sha2-0.11.x` - Merge into: `main` - Upgrade [sha2](https://github.com/RustCrypto/hashes) to `0.11.0` </details> <details> <summary>chore(deps): update rust crate jsonwebtoken to v10</summary> - Schedule: ["at any time"] - Branch name: `renovate/jsonwebtoken-10.x` - Merge into: `main` - Upgrade [jsonwebtoken](https://github.com/Keats/jsonwebtoken) to `10` </details> <details> <summary>fix(deps): update rust crate rmcp to v1</summary> - Schedule: ["at any time"] - Branch name: `renovate/rmcp-1.x` - Merge into: `main` - Upgrade [rmcp](https://github.com/modelcontextprotocol/rust-sdk) to `1.0` </details> <details> <summary>chore(deps): lock file maintenance</summary> - Schedule: ["* 0-3 * * 1"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `main` - Regenerate lock files to use latest dependency versions </details> --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-config-hash:00166b0bd151587ff6258f9f28139b8ed9769f828c3a8764a66a533831b625dc-->
renovate-bot force-pushed renovate/configure from a44cc437d1 to f187a87f5d 2026-05-07 15:07:08 +02:00 Compare
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/configure:renovate/configure
git switch renovate/configure

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff renovate/configure
git switch renovate/configure
git rebase main
git switch main
git merge --ff-only renovate/configure
git switch renovate/configure
git rebase main
git switch main
git merge --no-ff renovate/configure
git switch main
git merge --squash renovate/configure
git switch main
git merge --ff-only renovate/configure
git switch main
git merge renovate/configure
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ai/panelist!1
No description provided.