Release Notes

Release notes record what changed in each Nexa platform version so you can plan an upgrade with no surprises. Read the entry for every version between your current one and your target before you upgrade — breaking changes and required manual steps are called out per release. Newest version is at the top.

Each entry follows the same structure: Breaking changes (with the exact action you must take) come first, followed by new features, improvements, bug fixes, known issues, and upgrade notes. Versions follow semantic versioning: MAJOR.MINOR.PATCH. A MAJOR bump can contain breaking changes; MINOR adds features backward-compatibly; PATCH is fixes only.

Template

The entry below is a worked example of the format. Copy the heading structure for each real release. Keep every section even when empty (write “None”) so readers can trust that a missing item means “nothing changed”, not “not documented”.

v1.4.0 — 2026-07-10

Adds Snowflake as a first-class data platform alongside Databricks and moves agent authoring into its own API. Contains one breaking change to the connection secret layout — read the required action before upgrading.

Breaking changes

Change	Who is affected	Required action
Data-platform connection secrets moved from a single nexa-api-secrets Secret to per-service SecretProviderClass entries synced from your cloud secret store.	All deployments.	Before upgrading, add the new keys to your AWS Secrets Manager / Azure Key Vault secret and confirm each service’s SecretProviderClass references them. See Configuration Reference. The old flat Secret is ignored after this release.
Agent endpoints moved from nexa-backend to the new nexa-agents-api service.	Deployments using agents/automations.	Deploy the nexa-agents-api overlay and its namespace as part of this upgrade; update any external callers to the new base path.

Danger

Upgrade in the order given: land the secret-store changes and the new nexa-agents-api service in dev and test, validate, then promote to prod. Do not skip from an earlier minor directly to v1.4.0 if you are more than one minor behind — step through each release.

New features

• Snowflake data platform support. Deploy nexa-snowflake-api to run pipelines and agents against Snowflake, selected per environment. Databricks deployments are unaffected.
• Agentic automations promotion across environments (dev → test → prod) with change review.
• Cost tracking dashboards for warehouse and compute spend under Governance.

Improvements

• Rolling updates now wait on stricter readiness probes, reducing the chance of the web tier reaching an API that is still starting.
• Faster cold start for the API services (smaller runtime image layers).
• Clearer ArgoCD sync health for multi-service releases.

Bug fixes

• Fixed run_id not being returned from the Databricks API, which broke workflow log retrieval.
• Fixed PII tags being dropped when a source column was renamed during curation.
• Fixed a race where an automation could deploy before its dependent projection finished.

Known issues

• On very large glossary imports, the first page load after upgrade can be slow while the cache warms. Workaround: reload after ~30 seconds.
• Azure deployments: certificate renewal events are not yet surfaced in the Alerts view (tracked for a patch release).

Upgrade notes

Standard minor upgrade with one required secret-store action (above). Follow the Upgrade Guide — back up the application database first, upgrade non-production before production, and validate health endpoints after each service syncs.

v1.3.2 — 2026-06-18

Patch release. Drop-in; no required action.

Breaking changes

None.

New features

None.

Improvements

• Reduced ArgoCD sync noise for the dev and test environments.

Bug fixes

• Fixed intermittent 502s from the gateway during rolling updates of nexa-web.
• Fixed a config-reference typo that set the wrong default log level in test.

Known issues

None new since v1.3.0.

Upgrade notes

Patch upgrade — bump the image tags and sync. See the Upgrade Guide.

Related

Upgrade GuideSupported paths, step-by-step upgrade, validation, and rollback.

Configuration ReferenceConfig keys and secret layout referenced by breaking changes.