Repository navigation
fix(autofix): bind the sandbox image to its pulled digest #9527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 6 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
92c9a4e
fix(autofix): bind the sandbox image to its pulled digest
wenshao da1d9ad
fix(autofix): bind gate image inputs to the resolver step output (#9527)
wenshao 01452e0
fix(autofix): revert repo-hygiene binding outside PR footprint (#9527)
wenshao 65a541c
Merge origin/main into fix/autofix-sandbox-image-digest-9089 (#9527)
qwen-code-dev-bot 0ff059c
fix(autofix): harden sandbox image consumers per review round (#9527)
qwen-code-dev-bot 9c5e728
test(autofix): pin repair outcome gate, derive contract set (#9527)
qwen-code-dev-bot 495a13c
fix(autofix): pin resolver binary, make image check digest-aware (#9527)
qwen-code-dev-bot eb2988b
test(autofix): share resolver e2e scaffold, tripwire stale exemptions…
qwen-code-dev-bot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Critical] Make the pinned output the value the gates actually consume
None of the six
Resolve sandbox imagesteps has anid, and there is nosteps.<id>.outputs.imageconsumer anywhere in this commit, so this protected output is not addressable downstream. The agents and direct Docker verification still inheritQWEN_SANDBOX_IMAGEfrom appendableGITHUB_ENV; in a process-level reproduction, appending a second mutable value after resolution replaced the effective image while this pinned output remained unused. Give every resolver step an ID and bind every agent/gate image input directly to itsimageoutput; otherwise the pull-to-digest binding does not prevent post-resolution steering.中文说明
六个
Resolve sandbox image步骤均未设置id,当前提交中也没有任何steps.<id>.outputs.image消费者,因此这个受保护的输出无法被下游引用。Agent 和直接 Docker 验证仍从可追加的GITHUB_ENV继承QWEN_SANDBOX_IMAGE。进程级复现表明,在解析完成后追加第二个可变标签会覆盖实际生效镜像,而固定 digest 的 output 完全未被使用。应为所有解析步骤设置 ID,并让所有 agent/gate 直接绑定其image输出,否则该修复无法阻止解析后的镜像劫持。There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Split by footprint. In scope — resolved in
da1d9ad44b: bothResolve sandbox imagesteps inqwen-autofix.ymlandqwen-autofix-recovery.ymlnow carryid: 'sandbox_image', and every security-sensitive consumer in those jobs (Assess candidates,Develop fix,Triage and address,Repair deterministic rejection) bindsQWEN_SANDBOX_IMAGE: '${{ steps.sandbox_image.outputs.image }}'at step level, which outranks the appendableGITHUB_ENVvalue; the workflow contract test pins all of it. Out of scope — deferred and escalated: the identical defect inrepo-hygiene.yml(two resolver steps without ids, three env-inheriting consumers) is real, but that file is outside this PR's footprint and the deterministic gate rejected the previous commit precisely because it touched it — review feedback alone cannot authorize changes to CI machinery the PR never touched. The repo-hygiene change has been reverted byte-for-byte (01452e0358) and the binding is recorded in the deferred review findings queue so it survives merge. Open question for the maintainer: should the same id + step-level binding land inrepo-hygiene.ymlas a maintainer-owned change (direct commit or a small separate PR)? The contract test only needsrepo-hygiene.ymladded back to its workflow list once that lands.中文说明
按足迹拆分处理。范围内 —— 已在
da1d9ad44b中解决:qwen-autofix.yml与qwen-autofix-recovery.yml中的两个Resolve sandbox image步骤均已带id: 'sandbox_image',这些 job 中所有安全敏感的消费者(Assess candidates、Develop fix、Triage and address、Repair deterministic rejection)都在 step 级别绑定QWEN_SANDBOX_IMAGE: '${{ steps.sandbox_image.outputs.image }}',step 级 env 优先于可追加的GITHUB_ENV值;工作流契约测试已将上述全部接线固化。范围外 —— 延后并升级:repo-hygiene.yml中的同类缺陷(两个 resolver 步骤没有 id、三个消费者继承环境变量)确实存在,但该文件在本 PR 足迹之外,确定性门禁正是因为上一提交触碰了它而拒绝——仅凭审查反馈不能授权修改 PR 从未触碰的 CI 机制。repo-hygiene 的改动已逐字节回退(01452e0358),该绑定已记入延迟审查发现队列,确保合并后不丢失。给维护者的开放问题:同样的 id + step 级绑定是否应以维护者主导的改动(直接提交或单独的小 PR)落入repo-hygiene.yml?届时契约测试只需把repo-hygiene.yml加回其工作流列表即可。