Release Notes

Self-hosted-specific changes per Helm chart release — image bumps, Helm value changes, behavior shifts, and required operator actions

This page tracks self-hosted-specific changes for each Helm chart release: image tag bumps, Helm value additions or changes, runtime behavior shifts, and any action operators must take before or after upgrading.

For end-user product changes (UI, agents, documents), see What’s New. This page complements it — feature copy is not repeated here.

---

​

Unreleased

Unreleased

Helm chart v26.04.21 (Unreleased)

This entry is a placeholder. Final image bumps, Helm value changes, behavior shifts, and required operator actions will be documented here when v26.04.21 is tagged.

For the current state of v26.04.21 documentation, see the v26.04.21 Helm Values Reference.

​

April 28, 2026

Image UpdatesConfig ChangesBehaviorNew Capabilities

Helm chart v26.02.16.2 (Hotfix)

End-user changes shipped in this release line are documented at What’s New. Below are the self-hosted-specific changes.

Required action: minimal. Image bumps roll automatically on helm upgrade. Review the new Helm values below — none are required, but you may want to set them if you use Azure OpenAI GPT-5.1/5.2 or want to cap Dynamic Document generation.

Image updates

The following component images were bumped. If you pin tags explicitly in your values.yaml, update them; otherwise the chart defaults pull the new versions automatically.

Component	Previous (v26.02.16)	New (v26.02.16.2)
frontend_core	v26.02.16	v26.02.16.2
automation	v26.02.16	v26.02.16.2
ultron	v26.02.11.1-u	v26.02.16.2-u
hasura	v26.02.16	v26.02.16.2
litellm	v1.79.0-stable	v1.81.3-stable
boost	v26.02.16	v26.02.16.4
html_conversion	v26.02.14.1	v26.02.23.1

Configuration changes

New Helm values — all optional with sensible defaults. Add to your values.yaml only if you need to override.

Key	Default	Purpose
automation.env.DYNAMIC_DOCUMENT_GENERATION_LIMITATION	"" (unlimited)	Monthly per-company quota for Dynamic Document generation runs. Set to an integer to enforce a cap
openai.secretKeys.azure.AZURE_OPENAI_GPT_51_DEVELOPMENT_NAME	gpt-5.1	Azure OpenAI deployment name for GPT-5.1 — required only if you provision GPT-5.1 with a non-default deployment name
openai.secretKeys.azure.AZURE_OPENAI_GPT_52_DEVELOPMENT_NAME	gpt-5.2	Azure OpenAI deployment name for GPT-5.2 — required only if you provision GPT-5.2 with a non-default deployment name

See the Helm Values Reference for the full schema.

Behavior changes

LiteLLM proxy now forwards client headers and drops unsupported params. Two settings were added to the LiteLLM proxy config bundled with the chart:

• general_settings.forward_client_headers_to_llm_api: true — client request headers (e.g. trace IDs) are now passed through to the upstream LLM API. Review your egress policy if you previously assumed headers were stripped at the proxy.
• litellm_settings.drop_params: true — LiteLLM now silently drops request parameters not supported by the target model rather than rejecting the request. This improves cross-provider compatibility but means malformed parameters fail silently instead of erroring.

No values.yaml change is required — both settings ship enabled by default in the chart-managed config.

New capabilities

Azure OpenAI GPT-5.1 and GPT-5.2 are now wired into Ultron. The Ultron secret template now exposes AZURE_OPENAI_GPT_51_DEVELOPMENT_NAME and AZURE_OPENAI_GPT_52_DEVELOPMENT_NAME env vars. If you are running Azure OpenAI and have provisioned GPT-5.1 / GPT-5.2 deployments, the chart will pick them up via the values above.

References

• Helm chart tag: v26.02.16.2
• Upgrade guide
• Helm Values Reference

​

March 6, 2026

Image Updates

Helm chart v26.02.16.1 (Hotfix)

End-user changes shipped in this release line are documented at What’s New. Below are the self-hosted-specific changes.

Required action: none. Image bumps roll automatically on helm upgrade. No Helm value changes, no behavior changes.

Image updates

Hotfix to address Azure Cosmos DB index creation limitations encountered during database migration.

Component	Previous (v26.02.16)	New (v26.02.16.1)
automation	v26.02.16	v26.02.16.1
hasura	v26.02.16	v26.02.16.1

This release is superseded by v26.02.16.2. Operators on v26.02.16 should upgrade directly to v26.02.16.2.

References

• Helm chart tag: v26.02.16.1

​

February 16, 2026

Baseline

Helm chart v26.02.16 (Baseline)

This is the starting baseline of the v26.02.16 documentation line. Subsequent entries above describe the deltas from this release.

References

• Helm chart tag: v26.02.16
• v26.02.16 documentation