setup-pm tools-cache key stability in CI
Cluster 137805 · other. Data as of
Nothing open on GitHub. Fix merged in #141640 on 19 Oct 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 #141640. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #141640. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The three members all concern the setup-pm tools cache key in CI: one bug report says the key includes generated Python bytecode, and two fix-oriented pull requests aim to keep the key stable or restore cache hits. One of them references salvaging #132393. Titles alone do not show whether any change was merged or works.
Open issues0
Open PRs0
Fixes on record
-
#141640 fix(ci): setup-pm tools cache hits again (salvage #132393)
files:
.github/actions/setup-pm/action.yml
1 PR closed without merging
From the close comments: other 1
- #132393 fix(ci): keep the setup-pm tools-cache key stable across jobs · other
Closed issues · 1
- Closed#137805[Bug]: setup-pm tools cache key includes generated Python bytecode
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
- Subsystem
- other
- Merged PRs
- #141640
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Oct 2026