Skip to content

What’s new in Hedron 1.0

Hedron v1.0.0 is a subtractive, compatibility-reviewed stable release. It turns the proven 0.x capabilities into one canonical application model and freezes an enumerated stable surface. All 17 technical release gates are Verified; the Git tag and PyPI upload are complete.

One authoring model

New applications use three function roles:

Role Purpose Typical result
@app.page Complete navigable document Page or a component tree
@app.view Replaceable server-rendered region A view handle and HTML fragment
@app.action Typed server operation Refresh, redirect, toast, validation, or response

Feature composition uses app.include(...). The 0.67 screen, refreshable, fragment, command, form_command, and include_feature spellings are migration inputs, not parallel 1.0 authoring APIs.

Stability now has a precise boundary

The 1.0 SemVer promise applies to the machine-checked stable inventory, not every importable symbol. Public surfaces remain classified as stable, beta, experimental, internal, or deferred; capability readiness remains separately classified as Supported or Experimental.

Read Stability before depending on advanced APIs and What’s ready before making production claims.

HTMX, Alpine, and Web Components have one owner each

  • The server owns routes, authorization, CSRF, validation, durable state, and response HTML.
  • HTMX owns enhanced HTTP requests and placement of authoritative server HTML.
  • Alpine owns disposable browser-local presentation state.
  • Web Components own specialist internal DOM and typed element contracts.
  • Hedron coordinates lifecycle handoff without becoming a client application runtime.

The HTMX/Alpine boundary is normative for 1.0.

Package changes

  • hedron-core, hedron, edron, hedron-data, hedron-charts, and hedron-maps form the Stable 1.0.0 platform.
  • Host adapters, explorer, Posit, Workbench, and other vendor/tooling satellites remain Beta and are versioned and supported independently of the stable platform boundary.
  • hedron-workbench and hedron[workbench] were removed. Use hedron-posit / hedron[posit], or use fastapi-workbench for a plain ASGI application.
  • Charts, maps, native acceleration, MCP, Gradio, notebook, simulation, and sample-kit packages retain independent versions and their documented Beta/tooling boundaries.
  • Edron remains an independent authoring facade and requires Hedron >=1.0.0.

Migration tooling

Audit an application without importing or executing it:

python -m hedron --app app:app check --target 1.0 --project .
python -m hedron migrate api --target 1.0 . --out migrated-app

The migrator writes a new output tree and leaves dynamic or ambiguous cases for review. See the 1.0 upgrade guide for the exact mapping and rollback process.

Operational defaults that did not change

  • Polling remains the Supported production fallback; SSE and WebSocket helpers remain Experimental.
  • Production Explorer and plugin discovery remain deny-by-default.
  • Multi-worker jobs and caches require shared backends.
  • Session secrets are application-owned and must be passed explicitly.
  • Ordinary apps require no Node.js toolchain.
  • Automated accessibility evidence does not create an unqualified WCAG or human-AT claim.

Install status

Install the published release from PyPI:

python -m pip install "hedron>=1.0.0" "uvicorn[standard]"

Check Current release and support before changing an application pin.