Changelog
Rocky ships three artifacts on independent version numbers, so each keeps its own changelog. The canonical notes live in the repository and on the release pages below; this page just points you to them.
The three artifacts
Section titled “The three artifacts”| Artifact | Version tag | Changelog | Release page |
|---|---|---|---|
rocky CLI (engine) |
engine-v* |
engine/CHANGELOG.md | GitHub Releases |
dagster-rocky wheel |
dagster-v* |
integrations/dagster/CHANGELOG.md | PyPI |
| Rocky VS Code extension | vscode-v* |
editors/vscode/CHANGELOG.md | Marketplace |
Each changelog follows Keep a Changelog and the project uses semantic versioning.
Why three version numbers
Section titled “Why three version numbers”The CLI, the Dagster integration, and the VS Code extension are released separately because they move at different speeds and depend on each other loosely. The Dagster wheel and the extension both call the rocky binary as a subprocess, so a CLI release doesn’t force a release of the others. Tagging engine-v1.47.0 builds and publishes only the CLI; the Dagster and extension releases work the same way under their own tags.
Upgrading
Section titled “Upgrading”To upgrade the CLI to the latest release:
curl -fsSL https://raw.githubusercontent.com/rocky-data/rocky/main/engine/install.sh | bashPin a specific version by passing it to the installer:
curl -fsSL https://raw.githubusercontent.com/rocky-data/rocky/main/engine/install.sh | bash -s -- <version>