Deployments and revisions

Deployment

A deployment is one independently managed bot project with its own source, active revision, logs, KV data, scheduled tasks, and bot identity.

Deployments under the same bot can run at the same time. If two deployments react to the same event or register conflicting commands, both scripts are responsible for that overlap.

Disabling a deployment stops event handling, clears its application commands, and removes its scheduled tasks.

What Deploy does

The rocket action performs one controlled workflow:

  1. Reads the Weeble-managed workspace files and exact dependencies.

  2. Shows how many files were added, modified, or deleted.

  3. Builds and validates the bundle.

  4. Publishes an immutable revision.

  5. Warms and activates that revision.

Build warnings and failures appear in the Weeble output channel and as editor diagnostics when a file can be identified.

See Getting started for the complete output and screenshot.

Revision contents

Every published revision records:

  • Source files and the built artifact

  • Exact approved package versions

  • Publisher and timestamp

  • Release note

  • Source and artifact hashes

  • Git metadata when available

Editing workspace files never changes an existing revision.

Compare

Expand Revisions, then expand a revision to compare it with the previous revision. Select a changed file to open VS Code’s diff editor.

  • A means added.

  • M means modified.

  • D means deleted.

Use Compare Revision with Workspace to compare an older revision with files currently open in the editor.

Restore or activate

These actions are deliberately separate:

  • Restore Revision to Workspace replaces Weeble-managed local files with that revision. It does not deploy or change the running bot.

  • Activate Revision changes the running revision without modifying local files.

After restoring source, review the diff and deploy when you are ready. Activating an older revision does not delete newer revisions, so they can be activated again later.

Weeble retains the latest 25 revisions per deployment by default. Revisions required by active runtime or scheduled-task state are preserved in addition to that window.