Prepare v0.1.1 draft release

Author: Mygod

.github/workflows/release.yml

@@ -11,6 +11,11 @@ on:
         description: Exact 40-character commit SHA to release.
         required: true
         type: string
+      publish:
+        description: Publish the release after assets are verified. Leave false to prepare a draft.
+        required: true
+        default: false
+        type: boolean
 
 permissions:
   contents: read
@@ -148,7 +153,7 @@ jobs:
           vcpkg-triplet: ${{ matrix.vcpkg_triplet }}
 
   publish:
-    name: Publish immutable release
+    name: Create release
     needs:
       - validate
       - build-binaries
@@ -162,7 +167,7 @@ jobs:
         with:
           path: release-assets
 
-      - name: Create draft, attach assets, and publish
+      - name: Create draft, attach assets, and maybe publish
         shell: bash
         env:
           GH_TOKEN: ${{ github.token }}
@@ -171,6 +176,7 @@ jobs:
 
           version="${{ needs.validate.outputs.version }}"
           target="${{ needs.validate.outputs.target }}"
+          publish="${{ inputs.publish }}"
           artifacts=(
             slipstream-macos-arm64
             slipstream-macos-x86_64
@@ -228,6 +234,11 @@ jobs:
             fi
           done
 
+          if [[ "${publish}" != "true" ]]; then
+            echo "Draft release ${version} is prepared with all required assets."
+            exit 0
+          fi
+
           gh release edit "${version}" --repo "${GITHUB_REPOSITORY}" --draft=false
 
           immutable="$(gh api "repos/${GITHUB_REPOSITORY}/releases/tags/${version}" -H X-GitHub-Api-Version:2026-03-10 --jq '.immutable')"

CHANGELOG.md

@@ -2,5 +2,9 @@
 
 All notable changes to this project will be documented in this file.
 
+## v0.1.1 - 2026-05-20
+- Add CI-built Linux, macOS, and Windows binary release archives with checksums.
+- Add a GitHub Actions release workflow that prepares asset-backed draft releases.
+
 ## v0.1.0 - 2026-05-20
 - Initial public release.

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "slipstream-client"
-version = "0.1.0"
+version = "0.1.1"
 edition = "2021"
 description = "Slipstream DNS tunnel client CLI"
 license = "Apache-2.0"

crates/slipstream-client/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "slipstream-core"
-version = "0.1.0"
+version = "0.1.1"
 edition = "2021"
 description = "Core utilities for Slipstream"
 license = "Apache-2.0"

crates/slipstream-core/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "slipstream-dns"
-version = "0.1.0"
+version = "0.1.1"
 edition = "2021"
 description = "DNS codec for Slipstream's QUIC-over-DNS tunnel"
 license = "Apache-2.0"

crates/slipstream-dns/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "slipstream-ffi"
-version = "0.1.0"
+version = "0.1.1"
 edition = "2021"
 description = "FFI bindings and runtime helpers for picoquic in Slipstream"
 license = "Apache-2.0"

crates/slipstream-ffi/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "slipstream-server"
-version = "0.1.0"
+version = "0.1.1"
 edition = "2021"
 description = "Slipstream DNS tunnel server CLI"
 license = "Apache-2.0"

crates/slipstream-server/Cargo.toml

@@ -64,18 +64,20 @@ manually for a published release.
 gh workflow run release.yml \
   --repo Mygod/slipstream-rust \
   -f version=vX.Y.Z \
-  -f target=COMMIT_SHA
+  -f target=COMMIT_SHA \
+  -f publish=false
 gh run watch --repo Mygod/slipstream-rust
 ```
 
 Use the exact commit SHA that passed validation. Do not create or push a local
 Git tag first for this workflow.
 
 The workflow builds all six binary artifacts, creates a draft release, uploads
-the required assets, verifies the draft asset list, and only then publishes the
-release. Release immutability locks the tag and assets after publication, so a
-missing asset after publication means the release is bad and the fix is a new
-version.
+the required assets, and verifies the draft asset list. Leave `publish=false`
+to inspect the draft before publication. Use `publish=true` only when the
+release should be published immediately after the asset check. Release
+immutability locks the tag and assets after publication, so a missing asset
+after publication means the release is bad and the fix is a new version.
 
 - Verify the published release: