/drasi

Drasi version pinning - {project name}

Use this template as the durable versions.md artifact required by the Drasi skill's "Pin via a versions manifest" non-negotiable rule. Every field must be populated. CI gates parse this file to enforce pinned CLI version, apiVersion, drasi-lib crate version, MCP spec version, and image digest.

Pinned components

Last-checked date

YYYY-MM-DD (must be ≤30 days old at PR merge time)

Refresh trigger

• Quarterly review
• On any reported upstream release
• Before any production deployment

Approved exceptions

Record any approved deviation from the AI-context current_stable_version (for example, an explicit pin to a newer drasi-lib crate). Each exception MUST include: component, pinned value, AI-context value, rationale, approver, expiry date.

Cross-runtime compatibility

Populate this section only for projects that span more than one Drasi runtime form (for example, drasi-lib embedded in an edge service that feeds a Drasi Server hub, or Drasi for Kubernetes running alongside a drasi-lib worker). Single-runtime projects may skip this section.

CI gate (mixed-runtime projects)

When this section is populated, CI MUST Also, verify:

• drasi-lib crate version and Drasi Server / Platform image digest resolve to compatible drasi-core version lines per the project's compatibility statement above. The check parses crate metadata (cargo metadata --format-version 1 | jq -r ...) and the image digest's drasi-core SHA from release notes or the image's labels.
• MCP spec revision is identical on every component that exposes an MCP Reaction or agent endpoint.
• If the project pins to an upcoming-API-break version of drasi-lib (the Replayable Sources / Resumable Reactions rewrite), the "Approved exceptions" table above explicitly records that decision and the migration timeline.

A mixed-runtime project that does not populate this section fails the version- manifest CI gate.

Notes

• The pinned image digest MUST be the result of docker pull <image> followed by docker inspect <image> | jq -r '.[0].RepoDigests[0]' - never a floating tag.
• The pinned CLI version MUST be installed via an explicit release pin, not via curl | bash of an installer that pulls main.
• When the platform bumps apiVersion, run the apiVersion migration playbook in bundles/sources/guide.md and capture evidence in templates/drasi-upgrade-evidence.md before updating this manifest.