[BUG] Github Actions: claude-dedupe-issues.yml is failing
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I submitted a bug report and got an email that "Run failed: Claude Issue Dedupe - main (f860f67)"
Link https://github.com/anthropics/claude-code/actions/runs/20953909104
Looking at the Github Actions runs, the latest one which succeeded was https://github.com/anthropics/claude-code/actions/runs/20932250270 for issue https://github.com/anthropics/claude-code/issues/17764 yesterday at 19:28:04 GMT (16 hours ago)
Error: Unable to resolve action anthropics/claude-code-base-action@v1, unable to find version v1
... so I'm guessing the actual error is attempting to switch to an action which doesn't exist (yet?)
What Should Happen?
Github actions should succeed and any duplicates should be reported in the new ticket
Error Messages/Logs
Error: Unable to resolve action `anthropics/claude-code-base-action@v1`, unable to find version `v1`Steps to Reproduce
- Create a new issue
- Receive email with error message
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
yesterday at 19 GMT
Claude Code Version
n/a
Platform
Other
Operating System
Other
Terminal/Shell
Other
Additional Information
_No response_
4 Comments
There was a separate email about claude-issue-triage.yml also failing
https://github.com/anthropics/claude-code/actions/workflows/claude-issue-triage.yml
Probably broken by https://github.com/anthropics/claude-code/pull/17238, because https://github.com/anthropics/claude-code-base-action does not have a
v1tag yet.@ant-kurt @hackyon-anthropic
I'll use that opportunity and mention another incorrectly working github action https://github.com/anthropics/claude-code/issues/16497, probably stil unnoticed.
I have not observed this for my recent bug report, so assuming it got fixed.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.