Plugin lock failures from uv release-age checks on resvg-py
Cluster 128937 · agent. Data as of
Nothing open on GitHub. Fix merged in #137159 on 12 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #137159. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #137110. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members concern plugin installation and enablement in Hermes, where uv locking and release-age checks (including a resvg-py version lacking publish time metadata) are discussed. One item reports enablement being blocked, another proposes allowing compatible resvg releases during locks, and another discusses moving the release-age check to lock time; their outcomes are not established here.
Open issues0
Open PRs0
Fixes on record
-
#137110 Plugin installs work on any package mirror: release age is checked when Hermes locks (3 days), not on users' machines (#135589)
files:
plugin-catalog/README.md,pm/AGENTS.md,pm/environment.py,pm/workspace.py,pyproject.toml,tests/pm/test_workspace.py,tests/pm/test_workspace_build_inputs.py,tests/test_packaging_metadata.py,website/docs/developer-guide/plugins/catalog-submission.md,website/docs/developer-guide/plugins/index.md,website/docs/reference/package-management.md -
#137159 Core-only installs and hermes update work again on mirrors without upload times (regression from #137110)
files:
pm/workspace.py,tests/pm/test_workspace.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#128941 fix(pm): allow compatible resvg releases during plugin locks · superseded by another PR →
37725f2,9f63a6f,#137110,#137159
Closed issues · 1
- Closed#128937plugins enable fails: uv lock rejects resvg-py==0.4.0 (missing publish time) — blocks ALL plugin enablement
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.50: 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 Lab