Auth registry control for replacement provider plugins
Cluster 116668. Data as of
Nothing open on GitHub. Fix merged in #117655 on 21 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 #117655. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117655. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address how replacement provider plugins interact with the auth registry, specifically around aliases, display names, and ownership of ProviderProfile versus PROVIDER_REGISTRY responsibilities.
Open issues0
Open PRs0
Fixes on record
-
#117655 fix(auth): a user provider plugin's aliases and display name win in the auth registry (#116668)
files:
hermes_cli/auth_plugin_providers.py,tests/providers/test_auth_registry_mid_discovery.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#116695 fix(provider-auth): keep replacement plugins in control of auth · merged via another change →
5aeddb6,#117655
Closed issues · 1
- Closed#116668fix(provider-auth): replacement plugins can split ProviderProfile and PROVIDER_REGISTRY ownership
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
- #117655
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 21 Sep 2026