Renovate on Forgejo: Getting Dependency Update Pull Requests Without Dependabot
Elena Vasquez
November 15, 2026
One of the first things teams miss after moving from GitHub to a self-hosted Forgejo is Dependabot. On GitHub, a few lines of YAML get you pull requests whenever a dependency has a new version or a known vulnerability. On Forgejo there is no Dependabot, and without a replacement, dependencies quietly age until an upgrade becomes a project of its own.
The standard replacement is Renovate, an open-source dependency update bot that supports Forgejo and Gitea as well as GitHub and GitLab. This guide covers what Renovate does differently from Dependabot, the two common ways to run it next to Forgejo, a starting configuration, and the settings that keep the stream of pull requests manageable.
Why Dependabot doesn’t come with you
Dependabot’s update logic is open source, but the service that schedules it, reads your configuration and opens pull requests is built into GitHub. There is no supported way to point it at a Forgejo server. Some community scripts have tried, but they lag behind and are awkward to maintain.
Renovate was designed from the start to run anywhere. It talks to Forgejo through the API, so you can run it as a container on a schedule, as a job in Forgejo Actions or another CI system, or as a long-running service. It supports a very long list of package managers, including npm, pip and Poetry, Go modules, Cargo, Maven and Gradle, Composer, Docker images in Dockerfiles and compose files, Helm charts, GitHub Actions workflow versions, Terraform and more.
If you are still deciding whether to move, our Forgejo vs GitHub comparison covers the wider trade-offs.
A bot account and a token come first
Renovate acts as a user on your Forgejo server. Create a dedicated account, for example renovate-bot, so its pull requests are clearly labelled and its permissions are separate from any human’s.
- Create the user in Forgejo and give it a recognisable avatar.
- Add it as a collaborator with write access to the repositories it should update, or to a team in your organisation.
- Log in as the bot and create an access token with permissions to read and write repositories, issues and pull requests, plus read access to the user and organisation.
Also create a read-only GitHub personal access token from any GitHub account and keep it for later. Renovate uses it to fetch release notes and changelogs from GitHub for the packages it updates. Without one, it hits GitHub’s anonymous rate limit and your pull requests lose their useful release notes.

Option 1: a scheduled container
The simplest setup runs the official Renovate container on a schedule, from cron or a systemd timer on any machine that can reach your Forgejo server. The core settings are environment variables:
docker run --rm
-e RENOVATE_PLATFORM=gitea
-e RENOVATE_ENDPOINT=https://git.example.com/api/v1
-e RENOVATE_TOKEN=forgejo_bot_token
-e RENOVATE_AUTODISCOVER=true
-e RENOVATE_GIT_AUTHOR="Renovate Bot <renovate@example.com>"
-e GITHUB_COM_TOKEN=github_read_only_token
renovate/renovate
Renovate’s Gitea platform has long worked with Forgejo, because Forgejo kept API compatibility. Recent Renovate versions also accept forgejo as a platform name. Check the Renovate documentation for the version you run. RENOVATE_AUTODISCOVER=true makes the bot process every repository it has access to. You can limit it with RENOVATE_AUTODISCOVER_FILTER, or list repositories explicitly.
Run it every hour or a few times a day. Each run is stateless: Renovate checks each repository, compares dependencies with the latest versions and opens, updates or closes its pull requests.
Option 2: a Forgejo Actions workflow
If you already run Forgejo Actions, you can keep everything inside the forge. Create a small repository, for example infra/renovate, with a workflow that runs on a schedule and on manual dispatch. It should run the Renovate container or the renovate npm package, with the bot token stored as a repository secret. This puts the logs next to the code and makes it easy to trigger a run by hand after changing configuration.
Either option works. The scheduled container is easier to reason about if your runners are busy or still new; the Actions workflow is tidier once your runners are reliable. We compared Forgejo’s built-in CI with a separate system in Woodpecker CI vs Forgejo Actions.
The onboarding pull request
The first time Renovate sees a repository without configuration, it opens an onboarding pull request. It adds a renovate.json file and lists the dependencies it found and the updates it would propose. Nothing else happens until you merge it, which makes it a safe way to preview the bot’s behaviour.
A good starting configuration for a small team:
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": ["config:recommended"],
"timezone": "Europe/Berlin",
"schedule": ["before 7am on monday"],
"dependencyDashboard": true,
"packageRules": [
{
"matchUpdateTypes": ["minor", "patch"],
"matchCurrentVersion": "!/^0/",
"groupName": "minor and patch updates"
}
]
}
config:recommended is Renovate’s sensible default preset. The schedule keeps updates to one batch a week. The dependency dashboard is an issue in each repository that lists every pending, open and rate-limited update in one place, which Forgejo supports. Grouping minor and patch updates into a single pull request cuts noise dramatically.

Keeping the pull request flood under control
The most common complaint about dependency bots is volume. A few settings keep Renovate useful rather than exhausting:
- Group related packages. Use
groupNamewithmatchPackagePatternsor the built-in monorepo presets so, for example, all ESLint packages update together. - Limit concurrency.
prConcurrentLimitandprHourlyLimitcap how many pull requests can be open or created at once. - Automerge the boring ones. With tests in CI, you can set
"automerge": truefor patch updates of development dependencies. Renovate merges them only when the checks pass. Start with a narrow rule and widen it once you trust your tests. - Pin Docker images by digest where reproducibility matters, and let Renovate update the digest. This works well for compose files in a homelab repository.
- Separate major updates. Keep major versions as individual pull requests, with a label such as
breaking, so someone reads the changelog first.
Reviewing a Renovate pull request in a minute
A Renovate pull request is designed to be reviewed quickly. The description shows each package, the old and new versions, the type of update, links to the source, and release notes pulled from the project’s changelog. A good habit:
- Check the update type. Patch and minor updates rarely need more than green CI.
- For major updates, read the release notes in the description, looking for “breaking” sections and migration steps.
- Look at the changed lock file only if CI fails. Renovate updates lock files for you, so differences there are expected.
- Merge, or comment and close. If you close a pull request, Renovate won’t reopen it for that version, and the dependency dashboard records that you skipped it.
Lock files, monorepos and private registries
Renovate updates lock files such as package-lock.json, poetry.lock and go.sum by running the package manager itself, so the result matches what a developer would produce locally. In monorepos it finds every package file in the repository and can group updates across them. For example, the same library updated in several services can arrive in one pull request.
If your projects use private package registries, such as Forgejo’s own package registry for npm or containers, add credentials with Renovate’s hostRules configuration, stored as secrets rather than in the repository. Renovate can then see and update internal packages just as it does public ones.
Security updates without GitHub’s advisory database
On GitHub, Dependabot security updates rely on GitHub’s advisory database and alerts. Renovate can raise priority for vulnerable dependencies when it has vulnerability data. On non-GitHub platforms that typically comes from OSV, the open vulnerability database, enabled with the osvVulnerabilityAlerts option. It isn’t identical to GitHub’s alerts, so many teams add a scanner such as Trivy or a language-specific audit command to CI. Then a vulnerable dependency fails the build even before Renovate opens a pull request.
Running it in a homelab, not just for code
Renovate is not only for application code. Many homelab users keep their Docker compose files in a Forgejo repository and let Renovate open pull requests when an image has a new version. Combined with a deploy step, this turns “which of my thirty containers are out of date?” into a weekly list of pull requests with changelogs attached. It is far more controlled than auto-updating tools that pull new images silently at 3 a.m.
If you take that route, pair it with tested backups. Our guide to Docker Compose backup strategies covers what to copy and how to prove a restore works. That way a bad update is easy to roll back.
A setup that keeps dependencies boring
The aim of a dependency bot is to make updates small and routine, so they never pile up into a risky afternoon. A realistic setup for a small Forgejo instance is a bot account, a scheduled Renovate run, config:recommended with a weekly schedule, grouped minor and patch updates, automerge for low-risk changes once CI is solid, and a dashboard issue in each repository. It takes about an hour to set up, and it replaces most of what teams miss about Dependabot.