# Releasing robloxstudio-worktree
Releases must preserve the CLI's public contract, prove the Strain reference
flow against a real Studio instance, and ship the MPL-covered Rojo materials
with every native binary.
## 1. Prepare a clean release commit
Update `Cargo.toml` and `Cargo.lock` together when the version changes. Keep the
executable and package name `robloxstudio-worktree`, and do not rename commands,
configuration fields, placeholders, generated state, or managed attributes as
part of a routine release.
Run the repository checks with the minimum supported Rust version:
```bash
cargo +1.85.0 fmt --check
cargo +1.85.0 test --locked
cargo +1.85.0 clippy --locked --all-targets -- -D warnings
cargo +1.85.0 package --locked
cargo +1.85.0 publish --dry-run --locked
```
The final two commands must run without `--allow-dirty`. Inspect the package
contents with `cargo package --list` and confirm that it includes:
- `resources/RojoWorktree.rbxm`;
- `THIRD_PARTY_NOTICES.md`;
- `rojo/managed-autoconnect.patch`;
- the operational agent skill under `skills/robloxstudio-worktree/`.
## 2. Run live reference acceptance
Start the shared `robloxstudio-mcp` server, then run from the Strain checkout:
```bash
robloxstudio-worktree bootstrap
robloxstudio-worktree up --fresh --json
robloxstudio-worktree test -- --scenario Validation.suite_allows_current_catalogs --timeout 180 --verbose
robloxstudio-worktree down
```
Record the returned Studio instance ID and Rojo port. Acceptance is complete
only when the authored-place validation hook passes, the managed Rojo marker
matches the exact generated project, the gameplay test routes through that
instance ID, and `down` stops only that worktree's Studio and Rojo processes.
## 3. Tag and publish native binaries
Merge the release commit to `main`, verify CI is green, then create and push an
annotated tag that exactly matches the Cargo version:
```bash
git tag -a v0.1.0 -m "robloxstudio-worktree v0.1.0"
git push origin v0.1.0
```
The release workflow builds these host-native archives:
- `x86_64-unknown-linux-gnu` for Linux and WSL;
- `x86_64-pc-windows-msvc` for Windows;
- `x86_64-apple-darwin` for Intel macOS;
- `aarch64-apple-darwin` for Apple Silicon macOS.
Every archive contains the optimized executable, user, migration, and release
docs, MIT license, MPL third-party notice, exact Rojo source patch, and agent
skill. The workflow publishes a `SHA256SUMS` file with the archives.
Before tagging, run the `Release` workflow manually on `main`. Manual runs
exercise every host-native build and upload the archives as workflow artifacts,
but deliberately skip the public GitHub release job.
Download one release archive, verify its checksum, and run
`robloxstudio-worktree --version` before publishing the crate:
```bash
cargo publish --locked
```
Publishing the crate remains an intentional manual step so a pushed tag cannot
consume registry credentials or publish an irreversible version before its
native artifacts have been inspected.