Skip to content
TiketoTiketo Chat

Versions and updates

Exact published versions are immutable. Aliases are cached briefly and never overwrite an exact version.

Environment vX.Y.Z git-<sha> / git-<sha>-run-<run-id> stable latest
Production chatbot.tiketo.cloud yes, immutable release no yes, manually promoted release yes, newest production deployment
Staging staging.chatbot.tiketo.cloud no yes, immutable commit build no yes, newest staging deployment

Use production stable by default. Pin a production vX.Y.Z when you need fixed bytes, and use staging latest for current verification. This command shows the immutable build behind staging latest:

Terminal window
curl -fsS https://staging.chatbot.tiketo.cloud/embed/latest/manifest.json

Copy the manifest’s version value exactly and replace latest in every embed URL, such as /embed/<version>/loader.js. Do not build the value from a commit SHA. Staging usually uses git-<sha>, but a manual rerun uses git-<sha>-run-<run-id>. The manifest also lists each file’s SHA-256 digest. Record the resolved version in bug reports and test evidence. Ask your Tiketo contact for the pin if an older environment has no manifest.

Since v0.3.0, the manifest includes tiketo-chat.d.ts beside the loader. v0.1.0 and v0.2.0 do not include it. Use the same exact version for the loader and declarations. Do not use /embed/stable/tiketo-chat.d.ts until stable is at least v0.3.0.

The on, off, and reset commands and locale-aware labels also require v0.3.0 or newer. A pinned v0.2.0 loader can misread these calls as legacy initialization. Newer loaders warn about other unknown commands. Upgrade the loader before using the v0.3.0 API.

Before updating, review the changelog and Since vX.Y.Z notes. Test with the staging ID and origin, then update the production loader and declaration together.

A new or changed client-specific action or component contract needs a new embed version because validation is built into the loader. If your URL is pinned, update it to the version supplied by Tiketo. An older loader may ignore a new action or show component fallback.

Since markers

Section titled “Since markers”
  • v0.1.0: queue, initialization, launch context, and whereAmI.
  • v0.2.0: shared/host components, setFeature, one-shot replies.
  • v0.3.0: generated declarations, sticky on/off lifecycle events with stable error codes, logout-safe reset with optional relaunch, localized embed-owned UI, and explicit unknown-command handling.