Skip to content

Canon 26.10.2 — stable Agentic adoption

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Oct 19:47
· 9 commits to main since this release
v26.10.2
9586e1c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Stable Agentic adoption

Canon 26.10.2 adopts the published Agentic 26.10.1 wheel and aligns the server, Python SDK, and Java SDK versions. The HTTP schemas change only their version metadata. Canon's application code, migrations, Azure support, and existing RLM behavior remain unchanged.

pyfly stays at the qualified v26.09.04 reference. A later pyfly upgrade needs a separately qualified drain or replay of queued legacy EDA events; this release does not perform that cutover.

Install

For the server, follow Install the released server. The release requirements file selects the server wheel, qualified pyfly reference, and immutable public Agentic wheel. Use the matching source archive for the migration scaffold and runtime configuration. SHA256SUMS covers all eight package and operator assets.

Install the Python SDK directly from this release:

uv add https://github.com/fireflyframework/flycanon/releases/download/v26.10.2/flycanon_sdk-26.10.2-py3-none-any.whl

The Java SDK is available as com.firefly:flycanon-sdk:26.10.2 through GitHub Packages, with a downloadable JAR also attached here.

Verification

All seven required checks passed on the reviewed PR commit before the guarded merge. Local native validation passed 1,270 unit and integration tests; three optional Chroma/Qdrant cases were skipped because their clients were absent. Fresh installations from the public server requirements and Python SDK wheel passed, including all 59 SDK tests on Python 3.11.

The full installed application also passed authenticated ingestion, cited hybrid retrieval, tenant/workspace isolation, scoped agent-token refusals, and native PostgreSQL row-security checks in an owned local environment. That environment used an explicitly synthetic, deterministic loopback embedding service; it did not execute an external model. No paid provider calls or cloud application deployment were used. The container publisher verifies image publication separately from application runtime acceptance.

Earlier release tags and assets remain unchanged.

Full changelog

Assets 11
Loading