Release directories and publication
Publication makes an exact built candidate current for a component. Toolora exports the selected Git commit into a release directory, checks its identity and compatibility, and switches the component’s current link through the guarded release path. A successful build alone does not publish anything.
Frontend and API releases have independent identities. The release path must preserve changes already published to either component and match the applied schema. Release procedure describes the operator sequence; this concept explains the state changes and failure boundaries.
Candidate-to-current model
Section titled “Candidate-to-current model”flowchart LR Source[Exact Git commit] --> Export[Immutable source export] Export --> Build[Build and canary checks] Build --> Guard[Lock, identity and schema guards] Guard --> Current[Switch component current link] Current --> Verify[Health, readiness and version] Verify --> Outcome[Separately verify affected behaviour]
| State | What exists | What remains to establish |
|---|---|---|
| Source selected | Full commit and reviewed diff | Successful build and applicable checks |
| Candidate built | Release directory and build outputs | Publication compatibility and current-link switch |
| Canary checked | Candidate API starts under bounded build/test configuration | Normal scheduler/provider configuration and publication |
| Component current | Published directory selected under the shared lock | Health, readiness, version and affected outcome |
| Rollback selected | Previous compatible application directory | Compatibility with the schema that actually remains applied |
Identity, locking and preservation
Section titled “Identity, locking and preservation”The deploy scripts build from an exact Git archive rather than the mutable worktree. Dirty files, an unrelated checkout or a manually supplied version label must not become the deployed source. API dependencies are prepared for the exported candidate; frontend public configuration belongs to its build. The published SHA is more useful than the API’s static product-version label for source comparison.
The shared release lock prevents API, frontend and schema procedures from racing. Inherited lock descriptors are validated against the expected file/inode rather than trusted as arbitrary numbers. Preservation checks compare the candidate with currently published component identities so an older candidate cannot silently remove newer work. A squash merge can change commit ancestry without changing content; source and full-tree evidence must still establish the relevant identity.
Schema publication status is another prerequisite. A candidate that omits applied migration history or depends on unpublished schema must be refused. A current link or a green build cannot waive that boundary.
Failure and rollback
Section titled “Failure and rollback”Normal application publication checks the new component and can return to the previous compatible release if it fails. This does not undo a database migration, restore data or reverse a provider command. Schema publication deliberately uses forward-only failure handling after a schema change: an incompatible prior API must not be restarted simply because it was previously current.
The API build-only canary disables schedulers and uses bounded synthetic configuration. Its success proves startup under those conditions. Normal readiness and the affected authorized flow require their own checks. Treat a failure after a current-link change as a publication incident until actual link, version and process state agree.
Example and evidence scope
Section titled “Example and evidence scope”A synthetic candidate updates only handbook content. Packaging a clean static archive publishes no API, frontend or schema. An application candidate that changes a portal route needs a different path: review the exact source, publish the affected component and verify the route under the correct actor/resource scope. Neither action follows automatically from the other’s success.
Record candidate commit, component versions before/after, selected checks and the observed outcome. release.sh --check inspects prerequisites; it does not take a backup, pause writers or publish. Evidence interpretation and shared ownership prevent a build receipt or infrastructure label from becoming broader acceptance or authority.