Gitea

Not yet supported — provider = "gitea" is accepted as a configuration value, but the commands that talk to the forge are not implemented for Gitea yet.

Caution

With provider = "gitea":

• brel init errors — workflow scaffolding is only available for GitHub, GitLab, and Forgejo.
• brel release-pr errors — release PR creation supports only github, gitlab, or forgejo.
• brel tag in event mode errors — pass --tag (and optionally --target) for manual mode.

What works today

Commands that don’t touch the forge API work normally:

• brel validate — validates the config file.
• brel next-version — computes the next version from git history.
• brel changelog — generates the changelog with git-cliff or changelogen.
• brel tag --tag <tag> — manual tag creation and push (plain git push to origin).

Workaround: try the Forgejo provider

Forgejo is a fork of Gitea, and their APIs are still largely compatible. If your Gitea instance’s API matches, provider = "forgejo" may work — brel will use the Forgejo REST endpoints (pulls, issues) against your instance:

provider = "forgejo"
default_branch = "main"

[release_pr.version_updates]
"package.json" = ["version"]

You’ll need to supply the environment the Forgejo provider expects (BREL_FORGEJO_TOKEN, FORGEJO_SERVER_URL/GITHUB_SERVER_URL, FORGEJO_REPOSITORY/GITHUB_REPOSITORY), and adapt the generated Forgejo Actions workflow to Gitea Actions by hand — the two Actions systems are near-identical, but brel init won’t generate it for you.

This is unsupported territory: it depends on your Gitea version’s API compatibility with Forgejo. Test in a sandbox repository first.

Tracking support

First-class Gitea support (native provider + brel init scaffolding) is a natural next step given the Forgejo implementation. Watch the brel repository for progress, or open an issue describing your setup.