Cron execution context and authenticated principal for plugins
Cluster 130722. Data as of
Nothing open on GitHub. Fix merged in #133158 on 5 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 #133158. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #133158. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items relate to exposing cron execution context to plugins, specifically providing an authenticated execution principal so plugins can identify which cron run they are operating within. The work appears centered on a single feature tracked under issue #130722.
Open issues0
Open PRs0
Fixes on record
-
#133158 Plugins can tell which cron run they execute in: ctx.current_cron_execution() (#130722)
files:
cron/execution_identity.py,cron/scheduler.py,hermes_cli/plugins.py,tests/cron/test_cron_execution_identity.py,website/docs/developer-guide/plugins/index.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#130805 feat(cron): authenticated execution principal for plugins (#130722) · done elsewhere →
#133158
Closed issues · 1
- Closed#130722Authenticated cron execution principal for security-critical plugins
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
- #133158
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 5 Oct 2026