CLI changelog
The CLI release history covers project configuration, marketplace modules, staging and game
integration. Install the newest release with rudder update or from the download page.
Download the CLI
Run rudder agent init after updating to refresh the instructions in your game repository.
1.9.0 — 2026-11-07
Section titled “1.9.0 — 2026-11-07”- Build a project from marketplace modules through the CLI. Create and select a project, discover available modules, inspect their contracts and install compatible versions with their dependencies.
- Configure catalogs with schema inspection, paginated records, exact key lookup, record creation, version-checked updates, deletion and ordering.
- Manage currencies, apply module samples and upload images from files. JSON input also supports stdin with
--file -. - Read staging connection settings and configure allowed browser origins.
- Validate the complete draft and publish the checked revision to staging. Publication reports when the draft has changed since validation.
- Browse staging releases and generate TypeScript, C# or game server clients from an exact release with
--release-version. - Read command-specific help with
rudder help <command>or<command> --help. - Show release notes once after the first successful text command of a new CLI version. JSON commands and CI runs keep the notice pending.
Changed
Section titled “Changed”- Marketplace lists and catalog records support pages of 50 items by default, up to 200. Pass the returned
nextvalue with--cursorto continue. - Draft edits can expire a cursor. Restart from the first page after
cursor_expired. - JSON errors preserve validation problems and the current record when an update encounters
row_changed. - Content changes require staging. The CLI reports incompatible dependencies and staging configuration problems before publication.
- Agent instructions cover the complete marketplace-to-staging workflow. Run
rudder agent initafter updating to refresh the instructions in your game repository.
- Module inspection and installation use the same compatible-version selection for modules that are not installed yet.
- Explicit zero or negative
--release-versionvalues are rejected before connecting to the service.