Skip to content

fix: authenticate metaproxy image publishing - #4

Merged
3metaJun merged 1 commit into
metaproxy/v1.0.0-rc.21from
fix/ghcr-publish-permissions
Aug 27, 2026
Merged

fix: authenticate metaproxy image publishing#4
3metaJun merged 1 commit into
metaproxy/v1.0.0-rc.21from
fix/ghcr-publish-permissions

Conversation

@3metaJun

Copy link
Copy Markdown
Owner

📑 变更描述 / Description\n\nGHCR package metaproxy-newapi is a private user-scoped package with no linked repository. Its existing layers therefore reject the repository-scoped GITHUB_TOKEN with permission_denied: read_package, even though the workflow declares packages: write.\n\nUse the repository's GHCR_TOKEN secret for registry login. The secret contains a publisher credential with write:packages; no credential value is committed or printed.\n\n## 🚀 变更类型 / Type of change\n\n- [ ] 🐞 Bug 修复 (Bug fix)\n- [ ] ✨ 新功能 (New feature)\n- [x] ⚡ 性能优化 / 重构 (Refactor)\n- [ ] 📑 文档更新 (Documentation)\n\n## 🔗 关联任务 / Related Issue\n\n- No issue. This follows two failed release runs: 33104406497 and 33104667553.\n\n## ✅ 提交前检查项 / Checklist\n\n- [ ] 人工确认: 此说明由 Codex 协助整理,并非声称纯人工撰写。\n- [x] 非重复提交: 已检查当前 fork 的开放 PR。\n- [x] Bug fix 说明: 本 PR 未标记为 Bug fix。\n- [x] 变更理解: 已确认失败发生在 GHCR 读取既有私有层的授权阶段。\n- [x] 范围聚焦: 仅修改 metaproxy 镜像发布登录凭据来源。\n- [x] 本地验证: 已用同一凭据从本机成功推送完全相同的 tag。\n- [x] 安全合规: token 只存储于 GitHub Actions secret,未写入仓库或日志。\n\n## 📳 运行证明 / Proof of Work\n\n- Tag-triggered run 33104406497: image built; push failed with permission_denied: read_package.\n- Manual run 33104667553: reproduced the same permission failure.\n- Local authenticated push succeeded for �1.0.0-rc.21-metaproxy.3, digest sha256:20eee3665d679c45d11a9658b01dc36ef2a45c7d03dccf1c365956b8004d35e1.\n- GHCR_TOKEN is present in repository Actions secrets.

@3metaJun
3metaJun merged commit 0b16660 into metaproxy/v1.0.0-rc.21 Aug 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant