Release And Versioning

Issue 91 Edition 2026-04-01 3 min read

Not accepted General

Sources: 1 • Confidence: Medium • Updated: 2026-04-02 03:46

Key takeaways

datasette-enrichments-llm version 0.2a1 has been released.
When an enrichment is triggered, the triggering actor is passed through to the LLM call as the actor argument to llm.mode(...).

When an enrichment is triggered, the triggering actor is passed through to the LLM call as the actor argument to llm.mode(...).

What other functional, API, or compatibility changes (if any) are included in datasette-enrichments-llm 0.2a1 besides actor passthrough?
What is the exact type/structure and provenance of the "actor" value being passed to llm.mode(...) in this integration?
Does passing actor into llm.mode(...) change default behavior for existing deployments (e.g., different model selection, logging, access control), or is it inert unless user code consumes it?
Are there documented expectations about how enrichments should handle actor-based authorization, auditing, or rate limiting after this change?
Is there any direct operator/product/investor decision read-through in this corpus beyond "a new version exists" (e.g., recommended upgrade timing, deprecation timelines, or operational constraints)?

Actor passthrough into LLM calls may enable better auditing and access control features in the datasette and llm plugin ecosystem, which could support enterprise oriented usage if formalized and documented.
A new alpha release indicates ongoing development cadence for datasette-enrichments-llm, which may signal continued maintenance and potential near term API evolution for integrators managing dependency risk.

Release notes or documentation for 0.2a1 detailing additional changes, including any authorization, logging, or rate limiting guidance tied to the actor argument.
Downstream integrations or examples adopting actor based policy enforcement or audit trails in enrichment workflows, indicating the actor value is practically useful.
Follow on stable release or deprecation timeline that clarifies upgrade urgency and compatibility expectations for existing deployments.

Documentation clarifies actor passthrough is inert or purely informational with no supported patterns, reducing any security or enterprise read through.
Reports of compatibility breaks or unclear actor structure that create integration friction and slow adoption of the new version.
No additional functional changes beyond the actor argument and no subsequent stable release progress, suggesting limited roadmap impact.