{
    "version": "https://jsonfeed.org/version/1",
    "title": "NeoSpace — Release notes",
    "home_page_url": "https://docs.neospace.ai/release-notes",
    "description": "Updates for NeoSpace customers and integrators.",
    "items": [
        {
            "id": "https://docs.neospace.ai/release-notes/neospace-neodata-docs",
            "content_html": "<p>This update moves <strong>customer-facing release notes</strong> out of the documentation tree and into the <strong>blog plugin</strong>, so <code>/docs</code> stays focused on reference material while chronological updates live under <strong><code>/release-notes</code></strong>, similar to how many product teams publish changelogs (for example <a href=\"https://posthog.com/blog/tags/release-notes\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"\">PostHog</a> and <a href=\"https://docs.datadoghq.com/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"\">Datadog</a>).</p>\n<!-- -->\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"whats-new\">What's new<a href=\"https://docs.neospace.ai/release-notes/neospace-neodata-docs#whats-new\" class=\"hash-link\" aria-label=\"Direct link to What's new\" title=\"Direct link to What's new\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\"><strong>Blog-based releases</strong> — Each delivery is a dated folder in <code>blog/</code> with <code>index.md</code>, its own URL, and RSS/Atom feed support.</li>\n<li class=\"\"><strong>Clear separation</strong> — <a class=\"\" href=\"https://docs.neospace.ai/docs/intro\">Documentation</a> remains the long-lived product reference; <strong>Release notes</strong> are the timeline of what shipped.</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"improvements\">Improvements<a href=\"https://docs.neospace.ai/release-notes/neospace-neodata-docs#improvements\" class=\"hash-link\" aria-label=\"Direct link to Improvements\" title=\"Direct link to Improvements\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\">Room for <strong>screenshots</strong> under <code>static/img/release-notes/</code> when a release is best explained visually.</li>\n<li class=\"\"><strong>Authoring script</strong> — <code>npm run release-notes:new -- YYYY-MM-DD short-slug</code> scaffolds a new post (see <code>scripts/new-release.mjs</code>).</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"notes-for-administrators\">Notes for administrators<a href=\"https://docs.neospace.ai/release-notes/neospace-neodata-docs#notes-for-administrators\" class=\"hash-link\" aria-label=\"Direct link to Notes for administrators\" title=\"Direct link to Notes for administrators\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\">No change is required to SSO, API keys, or tenant configuration for this documentation-only update.</li>\n<li class=\"\">If your organization mirrors the site, update bookmarks from <code>/docs/release-notes/...</code> to <code>/release-notes/...</code> (post slugs are listed on the <a class=\"\" href=\"https://docs.neospace.ai/release-notes\">release notes index</a>).</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"next-releases\">Next releases<a href=\"https://docs.neospace.ai/release-notes/neospace-neodata-docs#next-releases\" class=\"hash-link\" aria-label=\"Direct link to Next releases\" title=\"Direct link to Next releases\" translate=\"no\">​</a></h2>\n<p>Future NeoSpace platform deliveries (NeoData, connectors, training, inference, and so on) follow the same pattern: add a new folder under <code>blog/</code> with <code>index.md</code>, tag with <code>release</code>, and publish with the site build.</p>",
            "url": "https://docs.neospace.ai/release-notes/neospace-neodata-docs",
            "title": "April 17, 2026 — Per-release documentation format",
            "summary": "NeoSpace public release notes now use the Docusaurus blog—one post per delivery, separate from reference documentation.",
            "date_modified": "2026-04-17T00:00:00.000Z",
            "author": {
                "name": "NeoSpace",
                "url": "https://www.neospace.ai"
            },
            "tags": [
                "Release"
            ]
        },
        {
            "id": "https://docs.neospace.ai/release-notes/engineering-quality-april-2026",
            "content_html": "<p>This note highlights <strong>how NeoSpace is built and verified</strong>, not a single product screen. The goal is <strong>predictable upgrades</strong> and <strong>faster fixes</strong> when something needs to change.</p>\n<!-- -->\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"whats-new\">What's new<a href=\"https://docs.neospace.ai/release-notes/engineering-quality-april-2026#whats-new\" class=\"hash-link\" aria-label=\"Direct link to What's new\" title=\"Direct link to What's new\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\"><strong>Unified frontend builds</strong> — Pipelines and tooling aligned so every release uses the same build commands and artifacts, shrinking “works on my machine” gaps.</li>\n<li class=\"\"><strong>QA and non-production routing</strong> — Safer ways to exercise token-based flows in dedicated environments, improving coverage before changes reach production traffic.</li>\n<li class=\"\"><strong>Repository hygiene</strong> — Removal of unused configuration and deployment scaffolding that could confuse operators or duplicate effort.</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"improvements\">Improvements<a href=\"https://docs.neospace.ai/release-notes/engineering-quality-april-2026#improvements\" class=\"hash-link\" aria-label=\"Direct link to Improvements\" title=\"Direct link to Improvements\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\"><strong>Less drift</strong> between staging and production build steps.</li>\n<li class=\"\"><strong>Clearer ownership</strong> of deployment workflows, which speeds up hotfixes and security patches.</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"notes-for-administrators\">Notes for administrators<a href=\"https://docs.neospace.ai/release-notes/engineering-quality-april-2026#notes-for-administrators\" class=\"hash-link\" aria-label=\"Direct link to Notes for administrators\" title=\"Direct link to Notes for administrators\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\"><strong>No tenant action</strong> is required solely because of these changes.</li>\n<li class=\"\">If your organization <strong>mirrors</strong> NeoSpace images or replayed build steps internally, align your CI with the same <code>npm run build</code> pattern your NeoSpace team publishes.</li>\n</ul>",
            "url": "https://docs.neospace.ai/release-notes/engineering-quality-april-2026",
            "title": "April 2026 — Release quality and validation",
            "summary": "Standardized builds, clearer QA paths, and less environment drift—so NeoSpace reaches production with fewer surprises.",
            "date_modified": "2026-04-13T00:00:00.000Z",
            "author": {
                "name": "NeoSpace",
                "url": "https://www.neospace.ai"
            },
            "tags": [
                "Release"
            ]
        },
        {
            "id": "https://docs.neospace.ai/release-notes/neodata-1-2-training-visibility",
            "content_html": "<p>The <strong>NeoData 1.2</strong> line is aimed at teams that run <strong>training</strong> at scale and need <strong>clear configuration</strong>, <strong>repeatable recipes</strong>, and <strong>better visibility</strong> into what the platform is doing.</p>\n<!-- -->\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"whats-new\">What's new<a href=\"https://docs.neospace.ai/release-notes/neodata-1-2-training-visibility#whats-new\" class=\"hash-link\" aria-label=\"Direct link to What's new\" title=\"Direct link to What's new\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\"><strong>Training and evaluation alignment</strong> — Configuration paths that tie training setup to evaluation more explicitly, so benchmarks and checkpoints match what you intended to measure.</li>\n<li class=\"\"><strong>Recipe-oriented training</strong> — Support for structured training “recipes” and overview surfaces that make complex setups easier to reuse and review.</li>\n<li class=\"\"><strong>Activity and monitoring</strong> — Refinements to how activity is presented in the portal, so operators can follow events without digging through internal logs.</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"improvements\">Improvements<a href=\"https://docs.neospace.ai/release-notes/neodata-1-2-training-visibility#improvements\" class=\"hash-link\" aria-label=\"Direct link to Improvements\" title=\"Direct link to Improvements\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\"><strong>Dataset experience</strong> — Fixes and polish around dataset naming and validation early in the 1.2 line, reducing confusion when many datasets are in flight.</li>\n<li class=\"\"><strong>Hosting and access</strong> — Streamlined front-door configuration for deployments that use a <strong>single domain</strong>, simplifying browser and cookie behavior for end users.</li>\n<li class=\"\"><strong>Queries and filters</strong> — Tighter behavior for training-related queries (for example foundation trainings), so lists reflect the right jobs and states.</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"notes-for-administrators\">Notes for administrators<a href=\"https://docs.neospace.ai/release-notes/neodata-1-2-training-visibility#notes-for-administrators\" class=\"hash-link\" aria-label=\"Direct link to Notes for administrators\" title=\"Direct link to Notes for administrators\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\">If you rely on <strong>schedule policies</strong> or automation around training windows, re-check schedules after upgrading to the latest 1.2 patch in your environment.</li>\n<li class=\"\">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.</li>\n</ul>",
            "url": "https://docs.neospace.ai/release-notes/neodata-1-2-training-visibility",
            "title": "April 2026 — NeoData 1.2: training clarity and operational visibility",
            "summary": "The 1.2 release line improves training configuration, recipe-oriented flows, and how activity is surfaced in the NeoSpace portal.",
            "date_modified": "2026-04-01T00:00:00.000Z",
            "author": {
                "name": "NeoSpace",
                "url": "https://www.neospace.ai"
            },
            "tags": [
                "Release"
            ]
        },
        {
            "id": "https://docs.neospace.ai/release-notes/neospace-platform-1-1",
            "content_html": "<p>NeoSpace <strong>1.1</strong> focuses on how teams <strong>stay informed</strong>, <strong>trust dataset processing</strong>, and <strong>keep integrations current</strong> as usage of the platform grows.</p>\n<!-- -->\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"whats-new\">What's new<a href=\"https://docs.neospace.ai/release-notes/neospace-platform-1-1#whats-new\" class=\"hash-link\" aria-label=\"Direct link to What's new\" title=\"Direct link to What's new\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\"><strong>Operational notifications</strong> — Slack-based alerts so your team can see important platform events without watching the console.</li>\n<li class=\"\"><strong>Dataset processing accuracy</strong> — Corrections so background processing reports the correct process identifier, improving traceability from UI to jobs.</li>\n<li class=\"\"><strong>Dependency security</strong> — Routine upgrades to core HTTP libraries used by the portal, reducing exposure to known vulnerabilities.</li>\n<li class=\"\"><strong>Integration groundwork</strong> — Ongoing work to connect NeoSpace with broader enterprise data and orchestration patterns (Cortex-related integration path).</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"improvements\">Improvements<a href=\"https://docs.neospace.ai/release-notes/neospace-platform-1-1#improvements\" class=\"hash-link\" aria-label=\"Direct link to Improvements\" title=\"Direct link to Improvements\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\">Clearer notification naming and behavior for day-to-day operations.</li>\n<li class=\"\">More predictable mapping between <strong>datasets</strong> and <strong>processing runs</strong> when you troubleshoot or audit workflows.</li>\n</ul>\n<h2 class=\"anchor anchorTargetStickyNavbar_Vzrq\" id=\"notes-for-administrators\">Notes for administrators<a href=\"https://docs.neospace.ai/release-notes/neospace-platform-1-1#notes-for-administrators\" class=\"hash-link\" aria-label=\"Direct link to Notes for administrators\" title=\"Direct link to Notes for administrators\" translate=\"no\">​</a></h2>\n<ul>\n<li class=\"\">No change is required to standard SSO or API usage for most tenants.</li>\n<li class=\"\">If you run <strong>custom automation</strong> against dataset or processing APIs, validate identifiers in non-production after this release window.</li>\n<li class=\"\">For connector or integration questions, use your usual NeoSpace support channel.</li>\n</ul>",
            "url": "https://docs.neospace.ai/release-notes/neospace-platform-1-1",
            "title": "March 2026 — NeoSpace platform 1.1",
            "summary": "Operational notifications, stronger dataset processing behavior, security maintenance, and integration updates—summarized for customer teams.",
            "date_modified": "2026-03-16T00:00:00.000Z",
            "author": {
                "name": "NeoSpace",
                "url": "https://www.neospace.ai"
            },
            "tags": [
                "Release"
            ]
        }
    ]
}