ASYRA

Releases / Framework milestones

Know exactly what your product composes.

Follow important Framework milestones, then inspect the current package family, supported environments, migration boundaries, and security guidance before composing or upgrading a product.

Current release
v0.5.0
Inventory
19 public packages
License
MIT
Supported composition
2D + CUSTOM

Release history

Important Framework milestones.

This history records releases that materially advance the public Framework. Smaller package and website updates will be tracked separately.

v0.5.0

Current

The public Framework foundation.

Asyra's first public Framework milestone brings its runtime model, package family, documentation, executable evidence, roadmap, and reference product into one discoverable release.

  • Composable runtime owners for intent, transactions, validation, persistence, and projections.
  • Official 2D composition plus an engine-neutral CUSTOM path.
  • Public documentation, Runtime Atlas, and Asyra Design as the reference product.

Current package inventory

Small owners. Explicit dependencies.

Choose only the package owners your product needs. Compare their current versions, public entrypoints, and Framework dependencies before composing or upgrading your product.

@asyra/ai-agent-runtime

0.5.1

.

None

@asyra/collaboration

0.5.4

.

@asyra/factory, @asyra/utils

@asyra/core

0.5.5

., ./canvas-pipeline-debugger, ./contracts

@asyra/factory, @asyra/feature-system, @asyra/input-system, @asyra/persistence, @asyra/props-manager, @asyra/reactive-events, @asyra/render, @asyra/render-engine, @asyra/scene-tree, @asyra/selection, @asyra/system-context, @asyra/ui-context, @asyra/utils

@asyra/design-system

0.5.3

., ./index.css

@asyra/utils

@asyra/factory

0.5.3

.

@asyra/reactive-events, @asyra/utils

@asyra/feature-system

0.5.3

.

@asyra/reactive-events, @asyra/utils

@asyra/input-system

0.5.4

.

@asyra/reactive-events, @asyra/utils

@asyra/persistence

0.5.2

.

@asyra/utils

@asyra/preset

0.5.6

.

@asyra/core, @asyra/reactive-events, @asyra/render-engine, @asyra/render-engine-pixi, @asyra/ui-context, @asyra/utils

@asyra/props-manager

0.5.3

.

@asyra/reactive-events, @asyra/utils

@asyra/reactive-events

0.5.3

.

@asyra/persistence, @asyra/utils

@asyra/render

0.5.5

., ./canvas-pipeline-debugger

@asyra/factory, @asyra/reactive-events, @asyra/render-engine, @asyra/scene-tree, @asyra/selection, @asyra/utils

@asyra/render-engine

0.5.1

., ./testing

None

@asyra/render-engine-pixi

0.5.2

.

@asyra/render-engine

@asyra/scene-tree

0.5.3

.

@asyra/props-manager, @asyra/reactive-events, @asyra/utils

@asyra/selection

0.5.2

.

@asyra/utils

@asyra/system-context

0.5.2

.

@asyra/utils

@asyra/ui-context

0.5.3

.

@asyra/scene-tree, @asyra/selection, @asyra/utils

@asyra/utils

0.5.1

.

None

Support and release boundaries

Environment, security, migration, and compatibility.

This guide explains the environment, security, migration, and compatibility boundaries of the current project package set. It does not announce or authorize publication, tagging, or deployment.

Candidate package set

The Framework package set contains exactly 19 public ESM packages. Package names, versions, exports, and dependencies are generated from the project manifests so this reference stays synchronized with the code.

Consumers may import only package roots and explicitly exported subpaths. Workspace aliases, workspace:*, hoisting assumptions, monorepo-only paths, and package-private src imports are not public contracts.

Supported environment

  • Node.js 24.x for package verification
  • Yarn 4.3.1 for repository contributors and release verification
  • public ESM entrypoints with TypeScript declarations
  • React 19 for Asyra Design and @asyra/design-system
  • Chromium through the current Playwright browser verification
  • official 2D and engine-neutral CUSTOM composition

Input System and default Core entries import without eager DOM access in the supported Node runtime. That proves import safety, not a public Headless Core, Core Kernel, server/worker lifecycle, no-Render dependency, or multi-runtime isolation.

Production 3D, HYBRID, auto layout, and unit-aware aggregation are not in this candidate.

Optional systems

Collaboration is opt-in. Without explicit composition, no provider, room, connection, timer, Awareness runtime, or network side effect exists. Apps own transport, authorization, persistence, recovery, and conflict policy.

AI is opt-in. Without explicit composition and invocation, no model provider, credential access, network request, timer, listener, or Feature registration exists. Apps own provider/backend policy, permissions, confirmation, action executors, and transactions.

Security reporting

Report suspected vulnerabilities through the repository's private GitHub security advisory. Do not disclose vulnerability details, credentials, provider tokens, document contents, or personal data in a public issue. This repository does not promise support through public issues or pull requests.

Migration and deprecation

App documents enter through core.setLoadSource(...) and app-owned migration before package-owner validation. These compatibility surfaces remain in the current candidate family and are planned for removal in the next major release:

Deprecated surfaceReplacement
core.setPersistence(provider)core.setLoadSource(source)
PixiJSRendererRenderAdapter from @asyra/render
RenderStrategyGraphicRenderGraphics
RenderStrategyEngineNeutralRenderStrategy

Runtime compatibility warns once where observable. Type-only aliases carry deprecation and replacement in declarations. New code should use replacements now; do not build new dependencies on compatibility names.

Repository release verification

For maintainers validating the complete repository from a clean Node.js 24.x checkout:

shell
yarn install --immutable
yarn react:build
yarn release:packages --prebuilt
yarn release:consumer
yarn release:records

Complete release acceptance additionally requires the project-owned tests, dependency checks, visual review, exact package artifacts, and registry-only consumer verification. Successful verification shows candidate readiness; it does not publish packages.

License

Asyra Framework packages are released under the MIT License. Include the copyright and permission notice in copies or substantial portions. The software is provided without warranty under the terms in the repository LICENSE.

Canonical sources