public/tea
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

ci(release): export TAG/BODY for python subshells #6

Merged
jmz merged 1 commit from maximus/fix/release-export-vars into main 2026-05-06 23:56:22 +00:00
Conversation 0 Commits 1 Files changed 1 +5 -2
jmz commented 2026-05-06 23:55:12 +00:00
Owner
Copy link

Trivial fix to release.yml: shell vars in a run: | block aren't visible to python3 -c subshells without export. Run 1481 failed with KeyError: 'TAG' for this reason. Just adds the export keyword.

After merge, the same fix needs cherry-picking onto release/mirus before re-tagging — Forgejo evaluates trigger filters from the tag's commit's tree, not the default branch (confirmed empirically on run 1481).

Trivial fix to release.yml: shell vars in a `run: |` block aren't visible to `python3 -c` subshells without `export`. Run 1481 failed with `KeyError: 'TAG'` for this reason. Just adds the export keyword. After merge, the same fix needs cherry-picking onto release/mirus before re-tagging — Forgejo evaluates trigger filters from the *tag's commit's tree*, not the default branch (confirmed empirically on run 1481).
ci(release): export TAG/BODY so python3 subshells can read them
All checks were successful
check / check (pull_request) Successful in 41s
Details
check / check (push) Successful in 48s
Details
215e5c0e0a 
Empirical: run 1481 failed at the create-release step with
'KeyError: TAG'. Root cause: shell vars in a 'run: |' block aren't
visible to subshells (python3 -c) without 'export'. Without it,
os.environ['TAG'] / os.environ['BODY'] both raise KeyError.

Fix: add 'export' to TAG and BODY assignments. The fastest way to
catch this in dev would have been a local 'bash -n release.yml' or
shellcheck on the rendered script, but neither runs here pre-push.
jmz merged commit 215e5c0e0a into main 2026-05-06 23:56:22 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
public/tea!6
No description provided.