Skip to main content

Deploys

Deploys are deliberate release actions. A commit or push alone does not publish Veoveo.

Operator Workflow​

  • Derive the affected scope before deploying.
  • State the intended deploy command before running it.
  • Prefer targeted deploys that match the diff.
  • Verify the public routes, APIs, assets, and docs that changed.

Verification Gates​

Verification gates: define the affected scope, run the relevant build or validation checks, perform the smallest appropriate deploy or config action, and verify the live user-facing or API behavior that changed.

For high-risk work, also prepare a rollback or follow-up plan before touching production.

Evidence To Capture​

  • Target environment and affected service, docs surface, API group, workspace, artifact, or operation.
  • Validation command or manual check performed.
  • Live route, API response, screenshot, or operation timeline proving the result.
  • Follow-up needed if verification is incomplete.

Media To Add​

  • Flowchart: affected plan, validation, deploy command, live verification, rollback decision. It helps operators avoid over-deploying. Source: release process.