feat: add automated crates.io publishing via GitHub Action

- Add custom publish-crates-io job to release workflow
- Runs after successful build, publishes automatically
- Includes error handling for existing versions
- Update announce job to wait for crates.io completion
- Improve release checklist with explicit CHANGELOG workflow steps

Author: Brandon Greenwell

.github/workflows/release.yml

@@ -408,16 +408,39 @@ jobs:
           done
           git push
 
+  publish-crates-io:
+    needs:
+      - plan
+      - host
+    runs-on: "ubuntu-22.04"
+    env:
+      CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
+    if: ${{ !fromJson(needs.plan.outputs.val).announcement_is_prerelease || fromJson(needs.plan.outputs.val).publish_prereleases }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+      - name: Publish to crates.io
+        run: |
+          echo "Publishing xleak to crates.io..."
+          cargo publish --token "${CARGO_REGISTRY_TOKEN}" || {
+            echo "::warning::cargo publish failed - version may already exist on crates.io"
+            exit 0
+          }
+
   announce:
     needs:
       - plan
       - host
       - publish-homebrew-formula
       - publish-scoop-manifest
+      - publish-crates-io
     # use "always() && ..." to allow us to wait for all publish jobs while
     # still allowing individual publish jobs to skip themselves (for prereleases).
     # "host" however must run to completion, no skipping allowed!
-    if: ${{ always() && needs.host.result == 'success' && (needs.publish-homebrew-formula.result == 'skipped' || needs.publish-homebrew-formula.result == 'success') && (needs.publish-scoop-manifest.result == 'skipped' || needs.publish-scoop-manifest.result == 'success') }}
+    if: ${{ always() && needs.host.result == 'success' && (needs.publish-homebrew-formula.result == 'skipped' || needs.publish-homebrew-formula.result == 'success') && (needs.publish-scoop-manifest.result == 'skipped' || needs.publish-scoop-manifest.result == 'success') && (needs.publish-crates-io.result == 'skipped' || needs.publish-crates-io.result == 'success') }}
     runs-on: "ubuntu-22.04"
     env:
       GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

CHANGELOG.md

@@ -14,7 +14,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - VIM mode `$` keybinding now correctly expects SHIFT modifier on Windows
 
 ### Added
-- Automated crates.io publishing via cargo-dist for all future releases
+- Automated crates.io publishing via custom GitHub Action for all future releases
 
 ## [0.2.4] - 2025-12-04
 

RELEASE_CHECKLIST.md

@@ -7,7 +7,10 @@ Use this checklist when preparing a new release of xleak. You can also create a
 - [ ] All tests passing: `cargo test`
 - [ ] No clippy warnings: `cargo clippy`
 - [ ] Code is formatted: `cargo fmt --check`
-- [ ] CHANGELOG.md updated with new version changes
+- [ ] CHANGELOG.md updated:
+  - [ ] Move items from `[Unreleased]` to new `[X.Y.Z] - YYYY-MM-DD` section
+  - [ ] Keep `[Unreleased]` section empty for future changes
+  - [ ] Verify changelog entries are accurate and complete
 - [ ] Version bumped in `Cargo.toml`
 - [ ] Test binary works: `cargo run --release -- test_data.xlsx`