Releases & Versioning

Enlace ships across four package ecosystems, each with a dev channel for fast iteration and a prod channel for real installs.

Package	Dev channel	Prod channel
Enlace.AspNetCore	GitHub Packages NuGet	NuGet.org
@get-enlace/ui, @get-enlace/express, @get-enlace/nest	GitHub Packages npm, dev dist-tag	npmjs.org, latest
enlace-spring-boot-starter	GitHub Packages Maven	Maven Central
enlace-fastapi	TestPyPI	PyPI

The dev channel exists for fast, low-ceremony iteration and isn't meant for production use — it updates on every merge to each repo's main branch, with no stability guarantee between builds. The prod channel is what real consumers should install: a deliberately slower-moving, versioned release.

What to install

Unless you're specifically tracking an in-progress feature, install from the prod channel — the plain dotnet add package Enlace.AspNetCore, npm install @get-enlace/express, npm install @get-enlace/nest, pip install enlace-fastapi, or the enlace-spring-boot-starter Maven dependency shown throughout these docs already point there by default.

Versioning

All packages follow semver. Enlace is pre-1.0 today, so expect the usual pre-1.0 caveat: minor version bumps may still include breaking changes until a 1.0 is cut. Each repo's own release notes (GitHub Releases on that repo) are the source of truth for what changed in a given version.

Status by adapter

• ASP.NET Core — actively developed, published to NuGet in enlace-dotnet.
• Express, NestJS — actively developed, both live in enlace-js.
• Spring Boot — actively developed, live in enlace-java, published to Maven Central.
• FastAPI — actively developed, live in enlace-python, published to PyPI.

Have an idea for what should come next? See Feature Requests.