v2.0.0
2.0.0 (2026-09-13)
Bug Fixes
-
adaptConfig() clobbered the dynamically-detected utilsDatabaseURI on its second call (bed64c3)
-
adaptService.js never rendered healthcheck.test placeholders (f23de34)
-
await health-check route registration to surface failures (00419cf)
-
bundled servable-redis-cache compose service disabled FLUSHDB, which its own consumer needs (33ae108)
-
depend on @servable/tools ^2.0.0 instead of the unischema dist-tag (67b116d)
-
guard adaptPort against services with no declared host port (ddabb6a)
-
implement device binding checks for refresh tokens and legacy sessions (04c40a3)
-
namespace host bind-mount data path collision, found via a real two-namespace boot (3a9976b)
-
remove target compose file if upAll fails, not just skip fingerprint write (a242fb2)
-
feat!: unischema - boot-time schema drift/compatibility-floor check, migration machinery removed (13f822c)
Features
- servableConfig.system.docker.namespace for per-worktree docker isolation (c85d547)
BREAKING CHANGES
- launchWithMigration/launchWithNoMigration-era boot behavior is
gone. Every app must have a committed servable.schema.json (viaservable schema build) before upgrading, or boot refuses with a clear error naming the fix.
Depends on @servable/tools@unischema (published under that dist-tag, not latest)
for the schema build/artifact primitives this relies on. Also configures a
unischema prerelease branch so this publishes under the unischema npm dist-tag
without moving latest.