Publish a version
Review an exact version
Choose a version from the workspace or history. The review screen shows its source digest and changes from its parent version. Publishing applies the complete selected module set, including intended deletions of code files.
The release sequence
- Lock the bot and compare its cloud revision with the saved baseline.
- Preview database changes against the selected local schema.
- Apply only supported, safe additive migrations.
- Verify the database is ready, then atomically publish the full module set with an expected revision.
- Read the cloud modules back and check the managed webhook.
If someone changed the bot in BotFather or another machine, publishing stops. Import the current cloud state and rebuild against that baseline rather than forcing an overwrite.
Partial or uncertain results
An interrupted connection does not prove a deploy failed. TeeAI records a needs-attention state. Retrying first compares cloud code with the chosen artifact and reconciles a completed deploy instead of blindly repeating it.
Compatible tables or columns added before a code failure are retained. Destructive changes and unknown migration types are blocked.
Verify in Telegram
A verified deployment confirms the code and webhook state, not every business scenario. Test /start, buttons, non-text input, multiple users, and data persistence. Cloud execution commands are not used as harmless local previews.