chore: Configure Renovate (Sebastian Software)

[jamesfastnerbot]

Renovate maintained by Sebastian Software GmbH — repository standards live at sebastian-software/standards.

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 and select the Retry/Rebase checkbox below. Renovate will update the Pull Request description the next time it runs.

---

Detected Package Files

• Cargo.toml (cargo)
• crates/morphea-cli/Cargo.toml (cargo)
• crates/morphea-core/Cargo.toml (cargo)
• .github/workflows/ci.yml (github-actions)
• 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
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• 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.
• 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
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• Evaluate schedules according to timezone Europe/Berlin.
• Shared Renovate preset for all Sebastian Software repositories.
• Drives the @sebastian-software/standards rollout: stamps .repometa.json#standards against the package's manifest.json#currentVersion and runs the mechanical sync. Variant A is in force — a human merges every standards: PR after the two external agent runs (apply-judgement + pre-review) have posted their commit/comment; this preset deliberately sets no automerge. The custom datasource reads currentVersion from the PUBLISHED npm package via unpkg (@latest), not from the standards repo main branch: the rollout integer can then never lead the CLI that postUpgradeTasks fetches via dlx, which removes the main-ahead-of-npm race (the older raw.githubusercontent.com/.../main source advanced the moment a feat PR merged, before release-please published, so apply could be handed a version that did not exist on npm yet). currentVersion stays the migration-ledger integer (it maps to changes/NNNN), so CLI-only releases — e.g. the 0.6.0→0.6.1 patch, both currentVersion 4 — still trigger zero rollout; only real standards changes do. unpkg serves @latest with a short CDN TTL (max-age=60 / s-maxage=300), far inside the worker's 4×/day cadence. Relies on Renovate following the unpkg 302 redirect to the resolved version (got default). If unpkg is unavailable the datasource yields no release and no PR is filed — a safe, self-correcting degradation rather than a wrong rollout. jsDelivr was rejected as the source because it caches @latest for up to 7 days.
• 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
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• Evaluate schedules according to timezone Europe/Berlin.
• Shared Renovate preset for all Sebastian Software repositories.

---

What to Expect

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

chore(deps): update rust crate image to v0.25.10

• Schedule: ["at any time"]
• Branch name: renovate/image-0.x-lockfile
• Merge into: main
• Upgrade image to 0.25.10

chore(deps): update actions/checkout action to v7

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-7.x
• Merge into: main
• Upgrade actions/checkout to v7

chore(deps): update github artifact actions to v7

• Schedule: ["at any time"]
• Branch name: renovate/major-github-artifact-actions
• Merge into: main
• Upgrade actions/upload-artifact to v7

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

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate.