Skip to content

Flycanon 26.10.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 17:59
· 22 commits to main since this release
v26.10.0
9d78dfd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Phone PII matching now respects hexadecimal identifier boundaries. Numeric fragments inside revision and digest identifiers no longer reject canonical memory writes. Standalone US and international phone numbers remain detected, and strict PII rejection remains enabled.

Server, Python SDK and Java SDK versions and runtime User-Agents are aligned at 26.10.0. The HTTP contract is unchanged. The release includes server and Python SDK wheels/source archives, the Java SDK JAR and SHA256SUMS.

Install the Python SDK directly from this release:

uv add https://github.com/firefly-operationOS/flycanon/releases/download/v26.10.0/flycanon_sdk-26.10.0-py3-none-any.whl

Server wheel: flycanon-26.10.0-py3-none-any.whl (Python 3.13). Java: com.firefly:flycanon-sdk:26.10.0 from GitHub Packages. Container: ghcr.io/firefly-operationos/flycanon:26.10.0 for Linux amd64 and arm64.

Validation includes the server PII regression suite, full server/SDK tests, native Docker integration, lint/type checks and the Docker image build. Cloud authentication and external provider acceptance are separate deployment checks. BuildKit SBOM/provenance publication is disabled; the workflow's attestation upload is advisory.

Standalone server installation

Use the verified server installation guide and versioned runtime requirements. A wheel installer does not consume repository uv-source settings: the requirements select PyFly v26.09.04 and Agentic v26.06.16 explicitly. A fresh full runtime installation resolved all 218 packages and served version 26.10.0; authenticated source/memory retrieval passed for two independently scoped project workspaces.

Keep the released source archive's pyfly.yaml, alembic.ini, migration directory and environment template in the runtime working directory. The configuration supplement is byte-identical to the released configuration. Starting without it can activate unintended framework defaults, including Kafka and a separate management listener. Configure the PostgreSQL database, credentials and provider settings for your operator environment before starting.

These installation supplements are documented in PR 78. The existing tag, wheel, source archives and Java package are unchanged; SHA256SUMS now covers all eight payload files. GHCR image access requires the registry package's permissions.

Assets 11
Loading