What's new​

• Blog-based releases — Each delivery is a dated folder in blog/ with index.md, its own URL, and RSS/Atom feed support.
• Clear separation — Documentation remains the long-lived product reference; Release notes are the timeline of what shipped.

Improvements​

• Room for screenshots under static/img/release-notes/ when a release is best explained visually.
• Authoring script — npm run release-notes:new -- YYYY-MM-DD short-slug scaffolds a new post (see scripts/new-release.mjs).

Notes for administrators​

• No change is required to SSO, API keys, or tenant configuration for this documentation-only update.
• If your organization mirrors the site, update bookmarks from /docs/release-notes/... to /release-notes/... (post slugs are listed on the release notes index).

Next releases​

Future NeoSpace platform deliveries (NeoData, connectors, training, inference, and so on) follow the same pattern: add a new folder under blog/ with index.md, tag with release, and publish with the site build.

What's new​

• Unified frontend builds — Pipelines and tooling aligned so every release uses the same build commands and artifacts, shrinking “works on my machine” gaps.
• QA and non-production routing — Safer ways to exercise token-based flows in dedicated environments, improving coverage before changes reach production traffic.
• Repository hygiene — Removal of unused configuration and deployment scaffolding that could confuse operators or duplicate effort.

Improvements​

• Less drift between staging and production build steps.
• Clearer ownership of deployment workflows, which speeds up hotfixes and security patches.

Notes for administrators​

• No tenant action is required solely because of these changes.
• If your organization mirrors NeoSpace images or replayed build steps internally, align your CI with the same npm run build pattern your NeoSpace team publishes.

What's new​

• Training and evaluation alignment — Configuration paths that tie training setup to evaluation more explicitly, so benchmarks and checkpoints match what you intended to measure.
• Recipe-oriented training — Support for structured training “recipes” and overview surfaces that make complex setups easier to reuse and review.
• Activity and monitoring — Refinements to how activity is presented in the portal, so operators can follow events without digging through internal logs.

Improvements​

• Dataset experience — Fixes and polish around dataset naming and validation early in the 1.2 line, reducing confusion when many datasets are in flight.
• Hosting and access — Streamlined front-door configuration for deployments that use a single domain, simplifying browser and cookie behavior for end users.
• Queries and filters — Tighter behavior for training-related queries (for example foundation trainings), so lists reflect the right jobs and states.

Notes for administrators​

• If you rely on schedule policies or automation around training windows, re-check schedules after upgrading to the latest 1.2 patch in your environment.
• No broad breaking changes to public integration contracts are called out for this line; confirm with NeoSpace if you embed the portal in iframes or custom shells.

What's new​

• Operational notifications — Slack-based alerts so your team can see important platform events without watching the console.
• Dataset processing accuracy — Corrections so background processing reports the correct process identifier, improving traceability from UI to jobs.
• Dependency security — Routine upgrades to core HTTP libraries used by the portal, reducing exposure to known vulnerabilities.
• Integration groundwork — Ongoing work to connect NeoSpace with broader enterprise data and orchestration patterns (Cortex-related integration path).

Improvements​

• Clearer notification naming and behavior for day-to-day operations.
• More predictable mapping between datasets and processing runs when you troubleshoot or audit workflows.

Notes for administrators​

• No change is required to standard SSO or API usage for most tenants.
• If you run custom automation against dataset or processing APIs, validate identifiers in non-production after this release window.
• For connector or integration questions, use your usual NeoSpace support channel.