V1.2 release validation status

V1.2 is unreleased. The full release-branch qualification matrix passed on 2026-10-21 at commit f443c76e822eef27b143d318d748ed513599e00c. The local qualification snapshot below is retained separately; neither result establishes compatibility with unqualified real external services.

#Completed CI qualification

The Mayura qualification workflow, run 39576846216, completed successfully on release-1.2 at the commit above. All 13 configured jobs passed, with zero failed jobs:

The consumer jobs include unit tests, packed consumers, runnable examples, templates, starters, package bundles, documentation, API/version checks, release archives and SBOM checks. Earlier failed or canceled attempts remain historical evidence; this result is a complete successful run on the recorded commit.

This documentation follow-up also incorporates newer main changes. The updated branch and the pull-request merge commit require their own qualification; the earlier green run is not evidence for those later commits.

#Completed local qualification

The local snapshot was completed on 2026-10-21 on Windows x64, using Node 24.14.1 for core checks and Node 24.15.0 for framework starter qualification.

These counts describe the completed qualification snapshot before this status page was added. Documentation edits are checked again during release preparation. The archives were staged for verification, not published; the release workflow must generate new archives bound to the final source commit and V1.2 version.

The integration result combines the latest execution of each case. The original all-service run had 54 failures and 313 skipped cases. Focused reruns cleared all executed failures, including a final serial run of 107 cases that cleared the remaining 52 failures. Filtered skips never overwrite an executed result. This is not a claim that the original full run passed or that skipped external profiles were qualified. Database stress cases passed without concurrent builds and unit-suite load. The subsequent complete CI pass is recorded separately above.

#Remaining qualifications and limitations

• Merge CI: the release-branch matrix passed at the recorded commit. Require green checks for the updated branch and pull-request merge commit, then qualify main, the only publishing branch, before releasing.
• Providers and gateways: offline transports and the provider harness dry run passed. Paid inference, real embedding endpoints, gateway accounting and remote discovery behavior have not been qualified.
• Authorization: OpenFGA, Cedar, Permit.io and Oso passed offline tests and package checks. Real provider/native engine interoperability, deployed policies and revision consistency remain host responsibilities and unqualified here. Amazon Verified Permissions is outside the implemented Cedar adapter.
• RAG: the experimental RAG surface passed offline tests, including fake vector transports/SQL executors and local SQLite native-memory checks. This does not establish real vector/reranker service compatibility, SQL query plans, deployment limits or read-after-write visibility on eventually consistent services.
• AG-UI: the experimental bounded profile passed adapter and native server tests. The opt-in reference HttpAgent/schema harness, CopilotKit compatibility and the notebook's rendered browser flow remain unqualified. Arbitrary in-flight paid-operation recovery, conversation branching, audio/video media and reasoning disclosure remain outside the profile.
• Frameworks and UI: framework builds, mounted HTTP approval/worker flows and offline packed server contracts passed. Shared Bun/Deno/workerd checks do not qualify the Hono-specific Bun/Deno or Workers/D1 application paths. Rendered browser interaction, visual/accessibility checks and live deployment qualification remain outstanding. See framework starters and copy-in UI.

Retain the experimental labels and these limits when publishing. Any claim of stable external interoperability requires the corresponding real-service or reference-client qualification before release; an offline pass is not sufficient evidence for that claim.

#Release preparation

1. Review the complete V1.2 implementation, validation fixes and updated documentation in the merge pull request from release-1.2 into main.
2. Require the documentation follow-up and merge commit to pass qualification; the earlier release-branch CI gate is complete at the commit recorded above.
3. Merge through the reviewed path into main, the only publishing branch, and require its qualification to pass.
4. Verify npm credentials or trusted publishing for the core package and extensions, the protected release environment, and the publishing enablement setting.
5. Dry-run the release workflow for 1.2.0 to regenerate versioned archives, checksums, SBOM and release notes from the final source. Publish and tag only through the approved release workflow.

Source manifests remain at 1.1.0 until the release workflow applies the coordinated version bump. The release branch has been pushed for review; V1.2 has not been tagged, published or deployed.