Skip to main content

llmhq-releaseops

Release engineering for AI agent behavior — bundle prompts, policies, and model configs into versioned artifacts, then promote them through gated environments.

Why This Exists

AI agents ship behavior through prompts, policies, and model configurations — not deterministic code. When something breaks in production, there's no git blame for "why did the agent start approving refunds it shouldn't?" ReleaseOps brings standard release engineering (bundle, promote, rollback, observe) to these behavior artifacts, so you always know what's running, what changed, and why.

Install

pip install llmhq-releaseops
Extra Install Adds
eval pip install llmhq-releaseops[eval] LLM-as-judge (OpenAI, Anthropic)
langsmith pip install llmhq-releaseops[langsmith] LangSmith trace queries
dev pip install llmhq-releaseops[dev] pytest, black, mypy

Quickstart

1. Initialize your project:

releaseops init

Creates .releaseops/ with environments (dev, staging, prod), bundle storage, and eval directories.

2. Create a bundle from your prompts and model config:

releaseops bundle create support-agent \
  --artifact system=onboarding:v1.2.0 \
  --model claude-sonnet-4-5 --provider anthropic

3. Promote through environments:

releaseops promote promote support-agent 1.0.0 dev
releaseops promote promote support-agent 1.0.0 staging
releaseops promote promote support-agent 1.0.0 prod

4. Load at runtime in your agent code:

from llmhq_releaseops.runtime import RuntimeLoader

loader = RuntimeLoader()
bundle, metadata = loader.load_bundle("support-agent@prod")
# bundle.model_config, bundle.prompts, bundle.policies — all resolved
# metadata is automatically injected into OpenTelemetry spans

5. Compare versions when something changes:

releaseops analytics compare support-agent@1.0.0 support-agent@1.1.0

Key Concepts

  • Bundle — immutable, content-addressed manifest of prompts + policies + model config (SHA-256 verified)
  • Environment — named deployment target (dev/staging/prod) with a pinned bundle version
  • Promotion — moving a bundle through environments with optional quality gates (eval, approval, soak)
  • Telemetry — automatic injection of bundle metadata into OpenTelemetry spans for production observability
  • Attribution — trace agent behavior back to specific prompt lines and policy rules that caused it

Documentation

  • IMPLEMENTATION.md — full CLI reference, Python SDK guide, data model reference, architecture details

License

MIT

Metadata

Release files for llmhq-releaseops 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for llmhq-releaseops 0.1.0
File Size Uploaded Provenance
llmhq_releaseops-0.1.0.tar.gz 59.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for llmhq-releaseops 0.1.0
File Interpreter ABI Platform
llmhq_releaseops-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 148.3 kB

Release files / llmhq_releaseops-0.1.0.tar.gz

Download URL llmhq_releaseops-0.1.0.tar.gz
Size 59.9 kB
Tags Source
SHA-256 checksum
How to use checksums
e87dc8ccbf93816e267ce23731bef2d77a51f7a0c1acd475e73344bbd4fcbdb7
BLAKE2b-256 checksum
How to use checksums
bd2c31124fc121206e06d21c40058cfaed78b00db3521c180ff77e8129e8930e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.3

Release files / llmhq_releaseops-0.1.0-py3-none-any.whl

Download URL llmhq_releaseops-0.1.0-py3-none-any.whl
Size 88.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
da4a278a2da49092f075b9c3039ff4e804704de7eba4a47bd58b002f07f4d724
BLAKE2b-256 checksum
How to use checksums
375a60b4a4ffa1a31a9e840b7be5068eb3a2859a4fcb8913952705b7ea48f544
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.3

Security for llmhq-releaseops 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page