Versions and releases
Choose a release, keep upgrades deliberate and find the full API contract.
Examples use the bot client from Your first bot.
SDK and API versions
SDK packages and the Bot API are versioned separately. These guides describe the current API v1 client. Pin a package version and commit your dependency lockfile for a repeatable deployment.
Read the release notes before upgrading. Before SDK 1.0, a minor version may change client behavior; patch releases are intended for compatible fixes. Existing versioned download archives remain unchanged.
Upgrade intentionally
Registry commands are available after the package’s publication is confirmed. If you installed a local archive, download the target version and install that archive explicitly.
Do not replace an already published version with different contents. Release a new version instead.
pnpm outdated @riscord/bot
pnpm update @riscord/botAPI compatibility and migration
The SDK uses Riscord’s API and event gateway. Other platforms’ bot clients are not drop-in replacements. Keep IDs as strings, map your existing permission requirements and use the Riscord command and interaction schema.
The API contract and migration guide are downloadable below. They are public and do not require a Riscord login.