Auto Triage fails on every new issue: `CLAUDE_CODE_OAUTH_TOKEN` reaches its triage step empty
维护者通常 5 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 66/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, typescript
调研方向
从 .github/workflows/auto-triage.yml 开始,重点查看 Run Claude triage 步骤以及它如何接收 CLAUDE_CODE_OAUTH_TOKEN。将该配置与失败运行的输出以及 action 预期的输入进行比较。当 workflow 能够使用已配置的凭据启动分类并应用 issue 标签时,任务即告完成;通过运行一次 workflow 进行验证。
由索引模型根据 Issue 内容生成。
描述
Before submitting a new issue
- I tested using the latest version of the library, as the bug might be already fixed.
- I tested using a supported version of react native.
- I checked for possible duplicate issues, with possible answers.
Bug summary
.github/workflows/auto-triage.yml runs on every opened issue and hands secrets.CLAUDE_CODE_OAUTH_TOKEN to anthropics/claude-code-base-action@beta. The secret reaches the "Run Claude triage" step empty, so the step fails before the triage starts, and the issue gets no label or comment. The workflow's runs succeeded until 2026-08-19 and have failed on every issue since 2026-09-09, while the file's last change is b5f2a4d (2026-04-16).
Library version
main at df32ce3
Environment info
System:
OS: Windows 11 10.0.26300
CPU: "(32) x64 AMD Ryzen 9 9950X3D 16-Core Processor "
Memory: 160.57 GB / 255.67 GB
Binaries:
Node:
version: 26.12.1
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 4.9.2
path: C:\Users\<user>\AppData\Roaming\npm\yarn.CMD
npm:
version: 12.2.1
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
Versions:
- 10.0.19041.0
- 10.0.26100.0
IDEs:
Android Studio: AI-262.9437.185.2621.16467767
Visual Studio: Not Found
Languages:
Java:
version: 17.0.20.1
path: C:\Program Files\Microsoft\jdk-17.0.20.101-hotspot\bin\javac.EXE
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 19.2.3
wanted: 19.2.3
react-native:
installed: 0.86.3
wanted: 0.86.3
react-native-windows: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
The workflow itself runs on GitHub Actions' ubuntu-latest; the block above is the machine reproduce.sh ran on.
Steps to reproduce
- Open any issue. The workflow's
issues: openedtrigger starts Auto Triage, and its "Run Claude triage" step fails; itsworkflow_dispatchinput starts the same run. - To read the runs without opening an issue, clone the reproducer branch, which is
mainat df32ce3 with one file added,reproduce.sh, and run it withghsigned in:git clone --branch repro/auto-triage-oauth-token https://github.com/YevheniiKotyrlo/react-native-css cd react-native-css bash reproduce.sh
reproduce.sh:
#!/usr/bin/env bash
# The secret auto-triage.yml hands its triage step, how its runs ended, the last change to the file, and the latest run's failing step
set -u
repository=nativewind/react-native-css
grep -n "CLAUDE_CODE_OAUTH_TOKEN" .github/workflows/auto-triage.yml
git log -1 --format="last change to the workflow: %h %cs" -- .github/workflows/auto-triage.yml
gh run list --repo "$repository" --workflow auto-triage.yml --limit 500 --json conclusion,createdAt \
--jq 'group_by(.conclusion)[] | "\(.[0].conclusion): \(length) runs, \(map(.createdAt) | min) to \(map(.createdAt) | max)"'
latest=$(gh run list --repo "$repository" --workflow auto-triage.yml --limit 1 --json databaseId --jq '.[0].databaseId')
echo "== run $latest"
gh run view "$latest" --repo "$repository" --log-failed |
grep -E "ANTHROPIC_API_KEY:|CLAUDE_CODE_OAUTH_TOKEN:|is required|##\[error\]" |
cut -f3-
Expected: the triage step starts with the token and labels the issue.
Actual: the step fails with Either ANTHROPIC_API_KEY or CLAUDE_CODE_OAUTH_TOKEN is required when using direct Anthropic API., and every run since 2026-09-09 has ended in failure.
The run's output on main at df32ce3, Windows 11, gh 2.103.3
15:# - CLAUDE_CODE_OAUTH_TOKEN: OAuth token from `claude setup-token` (Max subscription)
70: claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
last change to the workflow: b5f2a4d 2026-04-16
failure: 59 runs, 2026-09-09T17:16:25Z to 2026-11-05T16:01:43Z
success: 18 runs, 2026-04-17T01:13:05Z to 2026-08-19T13:31:10Z
== run 42060821561
2026-11-05T16:02:18.2790460Z ANTHROPIC_API_KEY:
2026-11-05T16:02:18.2790674Z CLAUDE_CODE_OAUTH_TOKEN:
2026-11-05T16:02:18.3440139Z ##[error]Action failed with error: Error: Environment variable validation failed:
- Either ANTHROPIC_API_KEY or CLAUDE_CODE_OAUTH_TOKEN is required when using direct Anthropic API.
2026-11-05T16:02:18.3464061Z ##[error]Process completed with exit code 1.
Reproducible example repository
https://github.com/YevheniiKotyrlo/react-native-css/tree/repro/auto-triage-oauth-token
- 主要语言
- TypeScript
- 星标
- 166
- 派生
- 45
- 平均合并
- 10 天 1 小时
- 30 天内合并 PR
- 4
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
nativewind/react-native-css 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
nativewind/react-native-css#563 ·
维护者通常 5 天内回复
-
`registerCSS` rejects the `debug: "verbose"` it passes on, and never calls a `logger` it is given未关闭
难度 2/5 1-3 小时 新手友好度 78/100
nativewind/react-native-css#562 ·
维护者通常 5 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
nativewind/react-native-css#561 ·
维护者通常 5 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
nativewind/react-native-css#559 ·
维护者通常 5 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
nativewind/react-native-css#558 ·
维护者通常 5 天内回复
查看 nativewind/react-native-css 的全部 Issue
相似的 Issue
-
Cleanup Setup可能已有人在做 @AlexanderKaran 今天认领。 未关闭documentation enhancement
难度 2/5 1-3 小时 新手友好度 64/100
e18e/framework-tracker#769 ·
维护者通常 1 天内回复
-
bug v2
难度 1/5 1 小时以内 新手友好度 88/100
modelcontextprotocol/servers#5483 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 84/100
XiaomiMiMo/MiMo-Code#2783 ·
维护者通常 1 天内回复
-
area: web bug
难度 2/5 1-3 小时 新手友好度 76/100
kinqsradio/orbyn-engineering#227 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
joeldesante/TurfBuilder#258 ·
维护者通常 1 天内回复