Skip to content

1.2.0 (docs/releases/1.2.0.md)

Digest

Preliminary publication: release-1.2 is not complete. This snapshot was published as stable before milestone acceptance was complete. The stable classification was withdrawn on 2026-10-08. Task #27 and Feature #8 still require genuine human translation reviews; stable publication requires the completed, closed milestone. The existing tag and audited assets are preserved for traceability.

F-Layer v1.2.0 makes its documentation easier to inspect and publish: every tracked file has an accountable place in the generated reference, and EN/RU/ZH-CN routes show their actual translation status. The documentation toolchain includes the setuptools security correction. Runtime and CLI behavior stay compatible with 1.1.0; Russian and Simplified Chinese prose remains explicitly draft.

What's Changed

Added

  • File and definition inventories that distinguish public installed-wheel APIs, rendered repository Markdown, locale overlays, and source-only engineering files.
  • Complete canonical Markdown navigation, including policy, ADR templates, architecture, development, release guidance, and the GitHub PR template.
  • Executable CLI and callable-protocol API coverage, whole-package wheel/source parity, exact anchors, local-link checks, and rendered-page reachability gates.
  • Implemented architecture diagrams and strict multilingual builds with localized navigation, draft/fallback banners, and 18 source-bound RU/ZH-CN draft pages.
  • A review handoff linking canonical sources, both locale drafts, required human roles, current source hashes, and publication evidence requirements.

Fixed

  • Broken generated links from repository review material to locale draft sources, with regression evidence for both languages and preserved fragments.
  • Snapshot installation instructions select v1.2.0 in English, Russian, and Simplified Chinese and retain the supported console/module commands.

Changed

  • New files in existing coverage categories are discovered automatically; unknown or ambiguous categories and missing wheel payloads fail validation.
  • Reviewed translation status remains separate from build success. Drafts and missing translations are labeled explicitly; automation creates no approvals.

Security

  • Pin setuptools 83.0.0 in the documentation toolchain for GHSA-h35f-9h28-mq5c / CVE-2026-59890, replacing vulnerable 80.9.0.
  • Preserve all other documentation pins, the Hatchling package backend, static API rendering, and existing ownership/mutation-consent boundaries.

Validation

  • The exact release candidate must pass full Python quality, strict multilingual documentation, and reproducible distribution CI. Local checks target the changed documentation, link rewriting, locale contracts, and package metadata.
  • Tagged publication verifies the annotated tag, exact master/source version, repeated byte-identical distributions, source-archive rebuild parity, owned members, metadata, and wheel RECORD hashes.
  • Audited wheel/source distributions and build evidence accompany publication; the evidence records the exact source commit, sizes, and SHA256 values.

Breaking Changes

None. Runtime APIs, CLI commands, owned-state contracts, and provider behavior remain compatible with 1.1.0. This release adds documentation and validation tooling.

Try it from source

git clone https://github.com/Fuzzy-Technologies/F-Layer.git
cd F-Layer
git checkout v1.2.0
python -m pip install .
flayer --help
python -m flayer check --format json

Python 3.11 or newer is required. The attached wheel is an alternative to source installation; a package-index upload is a separate owner-controlled operation.

Notes

  • Selects accepted release-1.2 PRs #46, #48, #59, and #60 on the tagged 1.1.0 baseline, plus bounded release stabilization. Plugin discovery, ecosystem integration contracts, and the static-site deployment profile remain later work.
  • All 18 authored RU/ZH-CN pages remain drafts. Generated APIs and untranslated repository material use explicit English fallback. Human editorial/technical reviews remain outstanding, so Task #27, Feature #8, and the milestone must be completed before a stable release can be published.
  • No live cloud deployment or PyPI upload is performed by this release.
  • Detailed changelog
  • Release provenance

Repository source