gravityfargo/uptime-kuma-api
Watch
1
0
Fork
You've already forked uptime-kuma-api
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity

chore: Configure Renovate #1

Open
renovate-bot wants to merge 1 commit from renovate/configure into master
pull from: renovate/configure
merge into: gravityfargo:master
Conversation 0 Commits 1 Files changed 1 +6
renovate-bot commented 2026-07-29 20:56:53 +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.

🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request.

📚 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

  • .forgejo/workflows/build-version.yml (github-actions)
  • .forgejo/workflows/checks.yml (github-actions)
  • .forgejo/workflows/pr-bump-preview.yml (github-actions)
  • .forgejo/workflows/test.yml (github-actions)
  • pyproject.toml (pep621)
  • .python-version (pyenv)
  • 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
  • If Renovate detects semantic commits, it will use semantic commit type build for all commits.
  • 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.
  • Disable digest and Git hash updates.
  • Disable Renovate Dependency Dashboard creation.
  • default base preset for Forgejo repos

What to Expect

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

build(deps): update dependency uv_build to >=0.12.0,<0.13.0
  • Schedule: ["at any time"]
  • Branch name: renovate/uv_build-0.x
  • Merge into: master
  • Upgrade uv_build to >=0.12.0,<0.13.0
ci(deps): update modernleft/commitizen-ci action to v0.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/modernleft-commitizen-ci-0.x
  • Merge into: master
  • Upgrade ModernLeft/commitizen-ci to 0.3.0
build(deps): lock file maintenance
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: master
  • 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.

⚠️ Warning

Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.

  • Failed to look up docker package code.modernleft.org/modernleft/general-ci: no-result
  • Failed to look up docker package code.modernleft.org/modernleft/commitizen-ci: no-result

Files affected: .forgejo/workflows/build-version.yml, .forgejo/workflows/checks.yml, .forgejo/workflows/pr-bump-preview.yml, .forgejo/workflows/test.yml

❓ 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 CLI.

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. 🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request. 📚 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 * `.forgejo/workflows/build-version.yml` (github-actions) * `.forgejo/workflows/checks.yml` (github-actions) * `.forgejo/workflows/pr-bump-preview.yml` (github-actions) * `.forgejo/workflows/test.yml` (github-actions) * `pyproject.toml` (pep621) * `.python-version` (pyenv) * `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 - If Renovate detects semantic commits, it will use semantic commit type `build` for all commits. - 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. - Disable `digest` and Git hash updates. - Disable Renovate Dependency Dashboard creation. - default base preset for Forgejo repos --- ### What to Expect With your current configuration, Renovate will create 3 Pull Requests: <details> <summary>build(deps): update dependency uv_build to >=0.12.0,<0.13.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/uv_build-0.x` - Merge into: `master` - Upgrade [uv_build](https://github.com/astral-sh/uv) to `>=0.12.0,<0.13.0` </details> <details> <summary>ci(deps): update modernleft/commitizen-ci action to v0.3.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/modernleft-commitizen-ci-0.x` - Merge into: `master` - Upgrade [ModernLeft/commitizen-ci](https://code.modernleft.org/ModernLeft/commitizen-ci) to `0.3.0` </details> <details> <summary>build(deps): lock file maintenance</summary> - Schedule: ["* 0-3 * * 1"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `master` - 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. --- > > ⚠️ **Warning** > > Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR. > > - `Failed to look up docker package code.modernleft.org/modernleft/general-ci: no-result` > - `Failed to look up docker package code.modernleft.org/modernleft/commitizen-ci: no-result` > > Files affected: `.forgejo/workflows/build-version.yml`, `.forgejo/workflows/checks.yml`, `.forgejo/workflows/pr-bump-preview.yml`, `.forgejo/workflows/test.yml` --- ❓ 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 CLI](https://github.com/renovatebot/renovate). <!--renovate-config-hash:87ef954a3c283e5ea88f5d2b3074b9d332f4100e00a9a1a20db57c6a63a95ac3-->
This pull request can be merged automatically.
This branch is out-of-date with the base branch
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 master
git merge --no-ff renovate/configure
git switch renovate/configure
git rebase master
git switch master
git merge --ff-only renovate/configure
git switch renovate/configure
git rebase master
git switch master
git merge --no-ff renovate/configure
git switch master
git merge --squash renovate/configure
git switch master
git merge --ff-only renovate/configure
git switch master
git merge renovate/configure
git push origin master
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
gravityfargo/uptime-kuma-api!1
No description provided.