feat(gitea)!: use Bearer instead of token for auth (#28308)

Previous Gitea implementation used non-standard “token” auth instead of “Bearer”. Gitea supports Bearer al alternate to token since v1.8.0, so it’s safe to make this change now. BREAKING CHANGE: Gitea platfor authentication will now be done using Bearer auth instead of token auth.
renovatebot · May 6, 2024 · 8654392 · 8654392
1 parent 1891c08
commit 8654392
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/lib/util/http/auth.spec.ts b/lib/util/http/auth.spec.ts
@@ -57,7 +57,7 @@ describe('util/http/auth', () => {
       expect(opts).toMatchInlineSnapshot(`
         {
           "headers": {
-            "authorization": "token XXXX",
+            "authorization": "Bearer XXXX",
           },
           "hostType": "gitea",
           "token": "XXXX",

diff --git a/lib/util/http/auth.ts b/lib/util/http/auth.ts
@@ -40,7 +40,9 @@ export function applyAuthorization<GotOptions extends AuthGotOptions>(
       options.hostType &&
       GITEA_API_USING_HOST_TYPES.includes(options.hostType)
     ) {
-      options.headers.authorization = `token ${options.token}`;
+      // Gitea v1.8.0 and later support `Bearer` as alternate to `token`
+      // https://github.com/go-gitea/gitea/pull/5378
+      options.headers.authorization = `Bearer ${options.token}`;
     } else if (
       options.hostType &&
       GITHUB_API_USING_HOST_TYPES.includes(options.hostType)