Renovate hardcodes poster=gitea-actions in Gitea API calls when running in Gitea Actions

[danshaw]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Running in docker using latest tag

Please tell us more about your question or problem

Hoping someone could shed some light on how I can get around this or if this is a known bug. I've done a lot of digging and can't seem to find a solution.

Summary:
Renovate hardcodes poster=gitea-actions in Gitea API calls when running in Gitea Actions, but this username is reserved in Gitea and cannot be created, causing all PR operations to fail with 400 Bad Request errors.

Bug Description:
Renovate hardcodes poster=gitea-actions parameter in API calls when running in Gitea Actions, but this username is reserved and cannot be created, causing 400 Bad Request errors.

Environment:

• Renovate version: latest (ghcr.io/renovatebot/renovate:latest)
• Platform: Gitea Actions (self-hosted)
• Gitea version: 1.23.8

Expected Behavior:
Renovate should use the configured username parameter instead of hardcoding gitea-actions.

Actual Behavior:
API calls fail with: user does not exist [uid: 0, name: gitea-actions]

Reproduction:

1. Run Renovate in Gitea Actions with any username configuration
2. Observe API calls use poster=gitea-actions regardless of config
3. API returns 400 error because gitea-actions is reserved

Workaround:
Use external Gitea URL instead of internal Docker networking to bypass the issue.I'm hoping someone could help me figure out

Logs (if relevant)

1. Renovate detects correct username but ignores it:

"config": {
  "hostRules": [], 
  "token": "***********", 
  "username": "renovate-bot"
}

2. API call shows hardcoded poster=gitea-actions despite config:

GET http://gitea:3000/api/v1/repos/danshaw-org/renovate-config/pulls?state=all&sort=recentupdate&limit=100&poster=gitea-actions

3. Gitea API error response:

{
  "name": "HTTPError",
  "code": "ERR_NON_2XX_3XX_RESPONSE", 
  "message": "Response code 400 (Bad Request)",
  "response": {
    "statusCode": 400,
    "statusMessage": "Bad Request",
    "body": {
      "message": "user does not exist [uid: 0, name: gitea-actions]"
    }
  }
}

4. Renovate successfully processes dependencies but fails on PR operations:

INFO: Repository finished (repository=danshaw-org/renovate-config)
       "durationMs": 8325,
       "updatesTotal": 1

[github-actions[bot]]

Hi there,

This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions.

No logs at all

If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.

Finding logs on hosted app

Select me to read instructions

If you use the Mend Renovate app (GitHub):

1. Log in to the Mend Developer Portal
2. Navigate to the correct organization and repository
3. Locate the appropriate log (it may not always be the latest one)
4. Copy/paste the log contents
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

Read the Renovate docs, troubleshooting, self-hosted to learn how to find the logs.

Formatting your logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here.

Good luck,

The Renovate team