All notable repository-level release changes are recorded here.
This project follows Semantic Versioning as defined in docs/VERSIONING.md.
- Breaking: HTTP handlers now use direct functions for simple routes and direct objects with a callable
runproperty for metadata-bearing routes. The publicdefineHandlerhelper has been removed.
- Added compile-time HTTP response-kind metadata, including the portable
response: "text"route option.
- Specialized security-header profiles by response kind to reduce request hot-path overhead for API and text responses.
- The globally installed Warbler CLI now delegates project commands to the project-local CLI, preventing duplicated runtime package registries and ensuring compiled views use the application's local dependency graph.
- Explicit
--projectpaths are normalized and delegated commands run from the resolved project root.
- Warbler begins lockstep versioning: the root release version, Git tag, GitHub release, and every publishable
@warblerjs/*package now share one release-train version.
Status: Draft, blocked
- Version 1.0 architecture and production launch audit.
- Version 1.0 release-candidate summary.
- Version 1.0 migration guide.
- Repository-level API reference index.
- Version 1.0 release notes draft.
- Deterministic
bun run release:audit:1.0audit command.
- Stable release is not approved while root
LICENSEtext is missing. - Stable release is not approved until the private security disclosure channel is recorded.
- Stable release is not approved while package versions remain
0.1.0-rc.0. - Stable release is not approved until
v1.0.0is tagged and packages are published by a release owner.
Status: Release Candidate preparation
- Repository-wide
bun run verifyrelease gate. - Repository validation and release validation scripts.
- CI verification workflow for typecheck, tests, benchmarks, and release validation.
- Root release checklist, release notes template, and final release audit.
- Publication metadata for
@warbler/core,@warbler/compiler,@warbler/runtime, and@warbler/http.
- Production package manifests now declare RC version metadata consistently.
- HTTP security and regression suites are callable through package-local scripts.
- Root security policy documentation was added.
- Existing HTTP security, Runtime conformance, and package-boundary checks are included in the unified gate.
- Root legal license text still requires project-owner approval before public publication.
- Published dependency ranges for internal Warbler packages must be converted from local development links during the publication step.
- Controlled CI benchmark baselines are still required before stable release certification.