chore: Configure Renovate #1

Merged

ses merged 5 commits from renovate/configure into main 2026-03-31 15:30:02 +00:00

Conversation 1 Commits 5 Files changed 6 +213 -5

renovate-bot commented 2026-03-31 10:56:00 +00:00

Collaborator

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.

---

Detected Package Files

• .devcontainer/devcontainer.json (devcontainer)
• .forgejo/workflows/release.yaml (github-actions)
• .forgejo/workflows/test.yaml (github-actions)
• pyproject.toml (pep621)
• .python-version (pyenv)
• 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
• 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
• 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.
• Group all minor and patch updates together.
• Automerge patch and minor upgrades if they pass tests.

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

---

You have configured Renovate to use branch main as base branch.

What to Expect

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

chore(deps): pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/dev-dependency
• Merge into: main
• Upgrade https://forge.sebatec.eu/actions/checkout to de0fac2e4500dabe0009e67214ff5f5447ce83dd
• Upgrade https://github.com/astral-sh/setup-uv to 37802adc94f370d6bfd71619e3f0bf239e1f3b78

chore(deps): update all non-major dependencies

• Schedule: ["at any time"]
• Branch name: renovate/all-minor-patch
• Merge into: main
• Upgrade python to 3.14
• Upgrade uv_build to >=0.11.2,<0.12.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

🚸 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 has been generated by Renovate Bot.

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. --- ### Detected Package Files * `.devcontainer/devcontainer.json` (devcontainer) * `.forgejo/workflows/release.yaml` (github-actions) * `.forgejo/workflows/test.yaml` (github-actions) * `pyproject.toml` (pep621) * `.python-version` (pyenv) * `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 - 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 - 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. - Group all `minor` and `patch` updates together. - Automerge `patch` and `minor` upgrades if they pass tests. 🔡 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. --- You have configured Renovate to use branch `main` as base branch. ### What to Expect With your current configuration, Renovate will create 3 Pull Requests: <details> <summary>chore(deps): pin dependencies</summary> - Schedule: ["at any time"] - Branch name: `renovate/dev-dependency` - Merge into: `main` - Upgrade [https://forge.sebatec.eu/actions/checkout](https://forge.sebatec.eu/actions/checkout) to `de0fac2e4500dabe0009e67214ff5f5447ce83dd` - Upgrade [https://github.com/astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) to `37802adc94f370d6bfd71619e3f0bf239e1f3b78` </details> <details> <summary>chore(deps): update all non-major dependencies</summary> - Schedule: ["at any time"] - Branch name: `renovate/all-minor-patch` - Merge into: `main` - Upgrade python to `3.14` - Upgrade [uv_build](https://github.com/astral-sh/uv) to `>=0.11.2,<0.12.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> 🚸 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`](https://docs.renovatebot.com/configuration-options/#prhourlylimit) for 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 [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-config-hash:7473a0c8bc9a05f91750376728d9cb1daf79672dfeefb9d4200e13d9af1ce1c0-->

renovate-bot added 1 commit 2026-03-31 10:56:00 +00:00

Add renovate.json b8da94ce2a

renovate-bot commented 2026-03-31 14:12:15 +00:00

Author

Collaborator

Copy link

Branch Conflicted

⚠️ This PR has a merge conflict which Renovate is unable to automatically resolve, so updates to this PR description are now paused. Please resolve the merge conflict manually.

### Branch Conflicted ⚠️ This PR has a merge conflict which Renovate is unable to automatically resolve, so updates to this PR description are now paused. Please resolve the merge conflict manually.

ses force-pushed renovate/configure from b8da94ce2a to aca894766d 2026-03-31 14:30:22 +00:00 Compare

ses added 1 commit 2026-03-31 14:31:43 +00:00

Use default configuration 01dea9352b

ses force-pushed renovate/configure from 01dea9352b to ee162c7d25 2026-03-31 14:57:29 +00:00 Compare

ses added 2 commits 2026-03-31 15:22:23 +00:00

docs: add test workflow Python matrix bean 76f6dfbed8

docs: update README installation section bean status f7d9f41165

ses added 1 commit 2026-03-31 15:28:30 +00:00

ci: simplify test workflow by removing Python version matrix ... bb02265108

We use system dependencies (python3-dbus) that are tied to the specific Python version available in Debian stable. Testing multiple Python versions causes issues because:

1. Different Python versions have different system package names
2. System dependencies may not be available for all Python versions
3. Production uses the default Debian stable Python version
4. Testing should match production environment

By using a single Python version matching Debian stable, we ensure:
- Consistent testing environment with production
- Proper system dependency availability
- More reliable test results
- Simpler CI configuration

Refs: forgejo-watcher-6yeu

Fix

ses merged commit bb02265108 into main 2026-03-31 15:30:02 +00:00

ses deleted branch renovate/configure 2026-03-31 15:30:02 +00:00

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

2 participants

Notifications

Subscribe

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

sebatec-eu/forgejo-watcher!1

No description provided.