Docker egress env-name collision guard coverage
Cluster 115646. Data as of
Nothing open on GitHub. Fix merged in #116721 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #116721. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116721. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where Docker egress collision guards only protected a subset of environment variable names (those matching *_API_KEY/*_TOKEN patterns), and work to extend the guards to cover all mapped credentials and env name spellings.
Open issues0
Open PRs0
Fixes on record
-
#116721 fix(docker): egress collision guard protects every mapped credential and every -e spelling (#115646, #115887, salvage #115647, #115888)
files:
tests/tools/test_docker_environment.py,tools/environments/docker_egress.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#115647 fix(docker): guard every egress-written env name in collision checks · merged via another change →
9182ad0,#116721,#115646,#115887,#115647,#115888
Closed issues · 1
- Closed#115646Docker egress collision guards only protect *_API_KEY/*_TOKEN env names
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #116721
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026