change to GH token

.gitea/workflows/renovate.yml

@@ -37,10 +37,11 @@ jobs:
           RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }}
 
           # Optional: GitHub token for accessing GitHub releases
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          # Note: Use GH_TOKEN not GITHUB_TOKEN (Gitea naming restrictions)
+          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
 
           # Logging
           LOG_LEVEL: info
 
           # Ensure we use the correct config
-          RENOVATE_REQUIRE_CONFIG: optional
+          RENOVATE_REQUIRE_CONFIG: optional

README.md

@@ -44,10 +44,21 @@ Documentation for the renovate-config repository explaining setup and usage.
 - Edit `config.js` to match your Gitea endpoint
 - Edit `autodiscoverFilter` to match your organization/user
 - Add `RENOVATE_TOKEN` as repository secret
-- Optionally add `GITHUB_TOKEN` for GitHub releases
+- Optionally add `GH_TOKEN` for GitHub releases (not `GITHUB_TOKEN` - see Gitea naming rules below)
+
+### Gitea Secret Naming Rules
+
+Gitea has specific rules for secret names:
+- Must contain only alphanumeric characters ([a-z], [A-Z], [0-9]) or underscores (_)
+- Cannot start with `GITHUB_` or `GITEA_` prefix
+- Cannot start with a number
+- Not case-sensitive
+- Must be unique at the repository level
+
+**Therefore**: Use `GH_TOKEN` instead of `GITHUB_TOKEN` for the GitHub access token.
 
 ## See Full Documentation
 
 For complete setup instructions, see:
 - [RENOVATE.md](../RENOVATE.md) - Full Renovate documentation
-- [Official Gitea Tutorial](https://about.gitea.com/resources/tutorials/use-gitea-and-renovate-bot-to-automatically-monitor-software-packages)
+- [Official Gitea Tutorial](https://about.gitea.com/resources/tutorials/use-gitea-and-renovate-bot-to-automatically-monitor-software-packages)