Commit c6d1fe2
fix: use gh CLI and Bearer auth for setup action latest version fetch
The 'Test Action (Latest Version)' CI job fails with HTTP 403 when
fetching the latest release via the GitHub API. The root cause is
that the action uses 'Authorization: token' header format, which
can be rejected on internal repositories.
Fix:
- Use gh CLI (pre-installed on runners) as primary method for
resolving the latest release — it handles auth natively
- Fall back to curl with the modern 'Authorization: Bearer' format
and proper Accept/API-Version headers
- Both approaches use the GITHUB_TOKEN already available in the env
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>1 parent 2aac716 commit c6d1fe2
1 file changed
+14
-7
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
54 | 54 | | |
55 | 55 | | |
56 | 56 | | |
57 | | - | |
| 57 | + | |
58 | 58 | | |
59 | 59 | | |
60 | | - | |
| 60 | + | |
61 | 61 | | |
62 | 62 | | |
63 | 63 | | |
| |||
66 | 66 | | |
67 | 67 | | |
68 | 68 | | |
69 | | - | |
70 | | - | |
71 | | - | |
72 | | - | |
73 | | - | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
74 | 81 | | |
75 | 82 | | |
76 | 83 | | |
| |||
0 commit comments