Skip to content
Run402 Docs

Releases and recovery

A release describes desired application state: database migrations/exposure, functions, static content, routes, assets and required secrets. The SDK prepares content and coordinates planning, staging and activation against the gateway’s verdicts.

replace and patch have different effects. Omitted slices can carry state forward; do not treat omission as deletion. Read the ReleaseSpec reference before synchronizing or pruning resources.

Terminal window
run402 up --check
run402 up --plan --project prj_example
run402 up --project prj_example
run402 deploy release active --project prj_example

A local check validates local inputs and reports deferred checks; it is not gateway validation. Planning determines remote policy, changes and warnings. Review any requested approvals. --allow-warnings approves broadly; prefer reviewing and allowing individual warning codes when appropriate.

Activation selects the staged release. SQL migration effects are not automatically reversed when you promote an older release. Failed work can be resumable; follow the operation handle and recovery guidance instead of starting a duplicate mutation. Bounded SDK retries apply only to conditions marked safe; a timeout alone is not permission to retry.

Automatic migration rehearsal is governed by the current plan, including skip reasons for a first deploy or unchanged migrations. Verification then checks application responses and serving evidence. An activated release, a pending edge and a verified app are distinct outcomes. See deploy and verify.

When a release is replaced, its previously public non-HTML files remain available at their original URLs for one hour when absent from the active release. Current routes and files always win. This lets an existing tab load an old fingerprinted chunk while new navigation uses the new release; it does not guarantee sessions lasting longer than an hour or compatibility between old JavaScript and new APIs.

Removed HTML is not retained. Reusing a path with different bytes serves the active bytes. Switching to explicit public paths also retains formerly public non-HTML URLs for the remaining interval. Plans report STATIC_PATHS_REMAIN_REACHABLE without requiring confirmation; static_continuity reports source identity and committed origin deadlines. Plans omit deadlines that do not exist yet. Cached copies may outlive the origin deadline. For accidentally published credentials, rotate or revoke them at the issuer and contact support for urgent containment.