chore: release 0.2.0

• [MSN] No active missions on the board
• [EXC] Board idle, no stories queued or active
• [HLT] 2 warnings, no structural errors detected

Author: rupurt

Cargo.lock

@@ -9,7 +9,7 @@ members = [
 resolver = "2"
 
 [workspace.package]
-version = "0.1.0"
+version = "0.2.0"
 edition = "2024"
 authors = ["keel contributors"]
 license = "MIT"

Cargo.toml

@@ -40,7 +40,7 @@ nix run github:spoke-sh/keel
 
 ```bash
 keel upgrade
-keel upgrade --ref v0.1.0
+keel upgrade --ref v0.2.0
 ```
 
 ### Manual Download

README.md

@@ -27,7 +27,7 @@ nix run github:spoke-sh/keel
 
 ```bash
 keel upgrade
-keel upgrade --ref v0.1.0
+keel upgrade --ref v0.2.0
 keel upgrade --ref 533fa5b8
 ```
 
@@ -58,24 +58,24 @@ Bump the version number in `Cargo.toml`. We follow [Semantic Versioning](https:/
 ```toml
 # Cargo.toml
 [workspace.package]
-version = "0.1.0" # Update this
+version = "0.2.0" # Update this
 ```
 
 ### 2. Commit and Push
 Commit the version bump to the `main` branch.
 
 ```bash
 git add Cargo.toml
-git commit -m "chore: bump version to 0.1.0"
+git commit -m "chore: bump version to 0.2.0"
 git push origin main
 ```
 
 ### 3. Create and Push a Tag
 Create a git tag corresponding to the new version (must start with `v`).
 
 ```bash
-git tag v0.1.0
-git push origin v0.1.0
+git tag v0.2.0
+git push origin v0.2.0
 ```
 
 ### 4. Automated Workflow

RELEASE.md

@@ -61,7 +61,7 @@ keel upgrade
 If you need a specific upstream tag or commit instead of the latest published release, Keel can build and install it through the same installer flow:
 
 ```bash
-keel upgrade --ref v0.1.0
+keel upgrade --ref v0.2.0
 keel upgrade --ref 533fa5b8
 ```
 

website/docs/start-here/install-keel.mdx

@@ -97,7 +97,7 @@ Typical upgrade commands:
 
 ```bash
 keel upgrade
-keel upgrade --ref v0.1.0
+keel upgrade --ref v0.2.0
 keel upgrade --ref 533fa5b8
 ```