Repository navigation
fix(release): the composed computers' state folder is the compose step's, since a job's env can't read the runner - #707
Merged
earakely-scale merged 2 commits intoNov 16, 2026
Conversation
…p's, since a job's env can't read the runner GitHub refused publish-pypi.yml since #705, as a job's own env named runner.temp, so v0.9.1542's tag started no release. The folder is set on the step that composes, and a test checks every workflow's job env reads only what a job can. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… not only its first Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/fd-5908-release-workflow-runner-context
branch
November 16, 2026 17:38
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What and why
GitHub has refused
publish-pypi.ymlsince #705: thecomputer-buildjob's ownenvnamed${{ runner.temp }}, and therunnercontext is only a step's. So thev0.9.1542tag started no release run (0 jobs), and every release until this lands is held up.What changes
XDG_STATE_HOMEmoves fromcomputer-build's jobenvto the env of its compose step, whererunner.tempis allowed.test_release_infra_images.pychecks that each workflow's job-levelenvreads only the contexts a job has (github,inputs,matrix,needs,secrets,strategy,vars). On the old file it fails namingcomputer-buildandrunner.How it was tested
context "runner" is not allowed hereon line 387 before; no errors after.tst/unit/test_release_infra_images.py: 59 passed.bump-version, so its merge cuts the release 1542's tag couldn't.🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge.Summary
Moves
XDG_STATE_HOMEto the compose step, whererunner.tempis allowed.Reviews (2) · Last reviewed commit: "test(release): every context a job env's..." · Reviewed by Greptile