This release includes 1 breaking change for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+12 more
Affected surfaces
ReleasePort's take
Light signalVersion v0.2.15 introduces an optional JINA_API_KEY environment variable to bypass anonymous rate limits during brand onboarding and mandates database migrations for Elmo Cloud compatibility.
Why it matters: Migrations are required for Elmo Cloud support; without setting JINA_API_KEY, brand‑onboarding flows hit rate limits.
Summary
AI summaryDatabase migrations are required for Elmo Cloud compatibility, and an optional JINA_API_KEY env var avoids rate limits during brand onboarding.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Breaking | High |
Requires database migrations for brand/org configuration changes to support Elmo Cloud Requires database migrations for brand/org configuration changes to support Elmo Cloud Source: llm_adapter@2026-07-16 Confidence: high |
— |
| Feature | Low |
Adds optional JINA_API_KEY env var to avoid anonymous rate limits during brand onboarding Adds optional JINA_API_KEY env var to avoid anonymous rate limits during brand onboarding Source: llm_adapter@2026-07-16 Confidence: high |
— |
| Bugfix | Medium |
Ensures overview charts use consistent timezone-specific x-axis Ensures overview charts use consistent timezone-specific x-axis Source: llm_adapter@2026-07-16 Confidence: high |
— |
Full changelog
What's Changed
- Add an optional
JINA_API_KEYenv var to avoid anonymous rate limits when fetching website content during brand onboarding. by @jrhizor - Ensure the overview charts use the same timezone-specific x-axis. by @jrhizor
- Changing some brand/org configurations behind the scenes to prepare for Elmo Cloud which requires db migrations (should run automatically on Docker Compose installations). by @jrhizor
NOTE: If you created brands using the admin API, you will have to run this for the db migration to work:
INSERT INTO "organization" ("id", "name", "slug", "created_at")
SELECT b."id", b."name", b."id", now()
FROM "brands" b
LEFT JOIN "organization" o ON o."id" = b."id"
WHERE o."id" IS NULL;
Full Changelog: https://github.com/elmohq/elmo/compare/v0.2.14...v0.2.15
Breaking Changes
- Database schema changes required for Elmo Cloud (run provided INSERT migration)
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Elmo (Open Source AEO)
All releases →Related context
Related tools
Earlier breaking changes
- v0.2.13 DELETE endpoints now return deleted resource directly instead of wrapper.
- v0.2.10 elmo start, stop, logs, build aliases removed; use elmo compose directly
- v0.2.10 ~/.elmo/config.json file removed; configuration moved entirely to .env
- v0.2.10 elmo telemetry command removed; DISABLE_TELEMETRY toggle now in .env
Beta — feedback welcome: [email protected]