CI: pin crate-ci/typos to @main, not @master - #3384
Conversation
crate-ci/typos's default branch is now main; master no longer exists upstream (verified via repos/crate-ci/typos/branches).
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
Overall Grade |
Security Reliability Complexity Hygiene |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| PHP | Sep 18, 2026 5:58p.m. | Review ↗ | |
| JavaScript | Sep 18, 2026 5:58p.m. | Review ↗ |
Important
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
Closes #3382
Broken:
.github/workflows/typos.ymlpinned thecrate-ci/typosaction to@master. Verified viarepos/crate-ci/typos/branchesthatmasterno longer exists upstream at all (onlymain, plus a couple of unrelated branches) — the workflow step is silently unresolvable as-is.Changed:
uses: crate-ci/typos@master→uses: crate-ci/typos@main. No other file in.github/workflows/referencescrate-ci/typos.Verified: confirmed
mainexists andmasterdoes not via the GitHub API branch list forcrate-ci/typos; push-then-CI is the self-test for this fresh branch (no red state to reproduce for a dead ref).