Commit 9922a41
fix: Use git protocol for retrace spec check (#92)
## Summary
- The Gitiles JSON API returns CAPTCHA/rate-limit pages on shared GitHub
Actions runner IPs, causing the retrace spec check to
[fail](https://github.com/getsentry/rust-proguard/actions/runs/24074103715/job/70218089282)
with `jq: parse error`
- Switch from Gitiles HTTP API to shallow `git fetch` + blob hash
comparison, which uses the git protocol and isn't subject to Google's
CAPTCHA gate
- Track the file's blob hash instead of the last commit hash — same
detection, no HTTP API dependency
## Test plan
- [x] Verified script runs successfully locally
- [ ] Verify the scheduled CI job passes
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>1 parent 269214b commit 9922a41
1 file changed
Lines changed: 17 additions & 12 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
4 | | - | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
5 | 7 | | |
6 | | - | |
7 | | - | |
8 | | - | |
9 | | - | |
10 | | - | |
| 8 | + | |
| 9 | + | |
11 | 10 | | |
12 | | - | |
13 | | - | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
14 | 19 | | |
15 | 20 | | |
16 | 21 | | |
17 | | - | |
18 | | - | |
| 22 | + | |
| 23 | + | |
19 | 24 | | |
20 | | - | |
21 | | - | |
| 25 | + | |
| 26 | + | |
22 | 27 | | |
23 | 28 | | |
24 | 29 | | |
| |||
0 commit comments