promote_strategy_versionPromote a specific version of one of your strategies to the stable or beta channel. Promoting to stable is the step that actually changes the code every bot on that channel runs — editing or validating a version has no effect on deployed bots until this is called. Optionally require a fresh version comparison showing the new version is not worse than the current stable one.
| Name | Type | Description |
|---|---|---|
id | string | Strategy ID |
versionId | string | The specific version to promote, from list_strategy_versions |
channel | string | Channel to promote into: stable (requires a passed validation) or beta (no gate) |
requireComparison | boolean | Stable only: refuse unless a fresh comparison against the current stable version says this version is not worse(default: false) |
minScoreDelta | number | Stable only, -100 to 100: minimum blended-score gain over the stable version; passing it turns requireComparison on(default: 0) |
presetId | string | Stable only: the comparison must have been run with this preset (unchanged since); passing it turns requireComparison on(default: no preset) |
force | boolean | Promote even when the comparison gate refuses; overrides only that gate, never validation(default: false) |
Try asking your AI assistant any of these:
compare_strategy_versionsBacktest a new version of one of your strategies and the current stable version on the same candles,
get_version_comparisonCheck a version comparison: progress while it runs, then per-pair and total metrics and scores for b
validate_strategy_versionRun the automated validation pipeline — syntax check, entry/exit logic check, and a quick real-data
list_strategy_versionsList the full version history for one of your own strategies — every stored version, its validation
Set up the TradeStaq MCP server in under a minute.