Skip to content

Devrouter 0.0.53

Choose a tag to compare

View all tags
@rschlaefli rschlaefli released this 05 Sep 19:15
v0.0.53
aba5287
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Upgrade to devrouter 0.0.53

Managed process adapters can prepare dependencies synchronously before launching
the background application. Exact managed Devsy stop can finish retained service
shutdown after the primary has stopped.

Task

  1. Install the published CLI with npm install -g @devrouter/cli@0.0.53 and
    verify devrouter-process --help advertises --prepare-command.
  2. Bump devrouter.version in the consumer .devrouter.yml to 0.0.53 when
    updating that repository's release pin. No schema migration is required.
  3. If dependency preparation currently consumes application readiness time,
    adapt the repository-owned managed adapter to call
    devrouter-process ensure --prepare-command <command> before its application
    command. Keep preparation in the foreground; do not daemonize or detach.
    Unchanged owned processes skip preparation. Explicit fingerprints remain
    caller-owned and must encode any required preparation identity.
  4. For an approved retained-runtime recovery, preserve required Compose
    interpolation settings and use devrouter stop <checkout>. A stopped primary
    is not sufficient shutdown evidence: require every project container stopped
    and zero checkout routes before guarded ensure --repair.

Validation

Verify installed/configured versions with devrouter -V --repo <checkout>.
Check preparation failure/cancellation, warm reuse, application readiness and
exact shutdown for the affected consumer. Preparation must finish before its
readiness deadline begins.

Stop validates ownership, configuration and complete container membership on
every mutation boundary. Changed, missing or unreadable evidence blocks cleanup.
An original provider failure is still reported after successful residual service
cleanup; inspect fresh state before choosing another operation. No containers,
volumes or runtime data are deleted. Repair retains its unchanged-configuration
guard and never creates missing resources or invokes provider bootstrap.

Report

Report installed/configured versions, exact checkout and retained profile,
preparation and readiness outcomes, all-container shutdown proof, route count,
and remaining blockers. Installing the package alone is not live recovery proof.

Assets 2
Loading