chore: release Bifrost Helm chart v2.1.33 with OTEL schema fix

[BearTS]

Summary

Fixes a Helm schema validation failure introduced in v2.1.32 where multi-profile OTEL configs (bifrost.plugins.otel.config.profiles) would fail with Additional property export_timeout is not allowed, blocking Helm render and deploy.

Changes

• Added export_timeout as an explicitly allowed (but deprecated) property in values.schema.json so that Helm's default map merge does not reject values when transitioning from the legacy flat config shape to the profiles wrapper shape.
• Commented out the export_timeout: 5 default in values.yaml to prevent it from being injected into the config and triggering the schema conflict.
• Added a warning to the v2.1.32 changelog directing users to use v2.1.33 instead.
• Published the v2.1.33 changelog documenting the fix.
• Bumped the Helm chart version to 2.1.33.

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

# Render the Helm chart with a multi-profile OTEL config to confirm schema validation passes
helm template bifrost ./helm-charts/bifrost \
  --set bifrost.plugins.otel.config.profiles[0].endpoint="http://otel-collector:4318" \
  --set bifrost.plugins.otel.config.profiles[0].export_timeout=10

# Should render without errors; previously would fail with:
# "Additional property export_timeout is not allowed"

Breaking changes

• Yes
• No

Related issues

Regression introduced in v2.1.32 by the addition of the export_timeout default value.

Security considerations

None.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ff729fd3-d405-42cb-9383-d6d9982acf60

📥 Commits

Reviewing files that changed from the base of the PR and between 5ada0fd and 2466964.

📒 Files selected for processing (7)

• docs/changelogs/helm-v2.1.32.mdx
• docs/changelogs/helm-v2.1.33.mdx
• docs/docs.json
• helm-charts/bifrost/Chart.yaml
• helm-charts/bifrost/README.md
• helm-charts/bifrost/values.schema.json
• helm-charts/bifrost/values.yaml

🚧 Files skipped from review as they are similar to previous changes (6)

• docs/docs.json
• helm-charts/bifrost/values.schema.json
• docs/changelogs/helm-v2.1.33.mdx
• helm-charts/bifrost/README.md
• helm-charts/bifrost/Chart.yaml
• docs/changelogs/helm-v2.1.32.mdx

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes
  • Fixed Helm schema validation failures affecting multi-profile OpenTelemetry configurations.
  • Stopped the chart from overriding the OpenTelemetry trace export timeout to allow rendering and deployment.
  • Maintained compatibility during the transition between legacy and multi-profile OpenTelemetry configuration formats.
• Documentation
  • Added Helm chart version 2.1.33 release notes, updated changelog navigation, and expanded guidance for the 2.1.32 validation issue (recommended upgrade to 2.1.33).
• Chores
  • Bumped the Helm chart version to 2.1.33.

Walkthrough

The Helm chart accepts export_timeout in the OTEL profiles wrapper for merge compatibility while removing its default rendered value. Chart metadata, navigation, README content, and changelogs are updated for v2.1.33.

Changes

Helm OTEL validation fix

Layer / File(s)	Summary
OTEL schema and rendered defaults helm-charts/bifrost/values.schema.json, helm-charts/bifrost/values.yaml	The profiles wrapper accepts integer export_timeout values from 1–60, while the chart no longer renders export_timeout: 5 by default.
Chart release and changelog updates helm-charts/bifrost/Chart.yaml, docs/changelogs/helm-v2.1.33.mdx, docs/docs.json, helm-charts/bifrost/README.md, docs/changelogs/helm-v2.1.32.mdx	The chart is versioned to 2.1.33, navigation and README entries are updated, and changelogs document the multi-profile OTEL schema-validation issue and fix.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• maximhq/bifrost#5540: Earlier OTEL export_timeout changes tied to this schema and rendered-config fix.
• maximhq/bifrost#5610: OTEL plugin and schema work involving the same export_timeout setting.

Suggested reviewers: akshaydeo, impoiler, roroghost17

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly names the Helm chart release and the OTEL schema fix, matching the main changes.
Description check	✅ Passed	The PR description covers the required sections with summary, changes, testing, type, impact, and related details.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 07-31-fix_export_timeout_default_values_removed_from_helm

---

_{Comment @coderabbitai help to get the list of available commands.}

[BearTS]

• chore: release Bifrost Helm chart v2.1.33 with OTEL schema fix #5705 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[akshaydeo]

Merge activity

• Jul 30, 9:08 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 30, 9:09 PM UTC: @akshaydeo merged this pull request with Graphite.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
bifrost	🔴 Failed	–	Jul 30, 2026, 9:09 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.