---
package: "@webjsdev/server"
version: 0.8.2
date: 2026-05-31T16:00:00+05:30
commit_count: 1
---
## Features

- **gate readiness on a fully warm instance; publish the pinned build id at boot** ([#147](https://github.com/webjsdev/webjs/pull/147)) [`8853e0a`](https://github.com/webjsdev/webjs/commit/8853e0a)
  `/__webjs/ready` now returns 200 only after the deterministic analysis AND
  the first vendor attempt have both completed, so a readiness-gated platform
  (Railway `healthcheckPath`, a k8s readinessProbe) admits traffic only once the
  importmap build id is settled, never mid vendor-resolution. A pinned app
  (committed `.webjs/vendor/importmap.json`) reads that map at boot and publishes
  its build id immediately, so a freshly-deployed pinned instance is detected as
  a new deploy with zero warmup window. The first vendor attempt is bounded by
  the jspm timeout, so an offline app still becomes ready shortly after.

## Fixes

- **stabilize the importmap build id across the warmup window** ([#147](https://github.com/webjsdev/webjs/pull/147)) [`8853e0a`](https://github.com/webjsdev/webjs/commit/8853e0a)
  Runtime-first boot resolved vendor lazily, so the `data-webjs-build` /
  `X-Webjs-Build` value changed across the first few responses (empty while
  warming, then resolved), and the client router treated that drift as a deploy
  and hard-reloaded, wiping form input on a fresh deploy. The server now
  advertises a PUBLISHED build id promoted only when the importmap is
  authoritatively final, and early requests await the first resolve so the first
  served response already carries the complete map. An empty id is reload-safe.
