Nexoraa Release Notes
Selected release notes for the Nexoraa platform, with emphasis on recent credits deployment hardening, gateway startup reliability, and database migration safety. This page is intended to read like a normal product release note rather than an audit stub.
Release Summary
This release focuses on making production deploys more deterministic, improving the resilience of the credits environment, and reducing the number of hand-maintained steps required on the box.
Versioned Changelog
Release notes page published at a stable public URL and updated to present the latest platform changes in a release-note format.
Consolidated June changes focused on deploy determinism, gateway startup reliability, and database migration hardening.
What's New
Credits deploys now build a deployable SHA image and publish by immutable image digest rather than a moving tag.
Gateway environment setup is seeded during deploy so services come up with the runtime values they expect.
Alembic deploy commands were tightened to avoid quoting and URL normalization issues during batch database upgrades.
Unchanged images are skipped, stale pulls are pruned quietly, and cache-export failures no longer block the deploy path.
Improved
- Credits deploys are now more repeatable because the workflow prefers immutable image SHAs over mutable tags.
- Gateway services start with the expected environment wiring, reducing hand-maintained setup on the host.
- Batch database deploy steps are safer and easier to reason about because the Alembic invocation is normalized and quoted correctly.
- Deploy noise has been reduced by skipping unchanged images and ignoring non-critical cache export failures.
Fixed
- Resolved deploy instability caused by shell quoting in batch Alembic commands.
- Resolved a class of deploy failures where gateway environment values were missing during startup.
- Resolved unnecessary deploy churn from image rebuilds that did not change the resulting runtime artifact.
- Resolved operational blockers where CloudFormation IAM differences should not have stopped the Credits deploy path.
Operational Follow-Up
- Continue adding release entries when deploy behavior changes materially.
- Keep public notes concise and release-focused rather than process-focused.
- Retain the public URL as the stable source of truth for externally shared release notes.
Reference Notes
These notes summarize the changes visible in the repository history for June 2026. They are intentionally concise and focus on release-impacting behavior rather than internal compliance process language.
Current document build: 2026-06-30