ci: trigger cargo publish from release workflow

[danbugs]

Summary

• Add cargo-publish.yml dispatch to release.yml (same pattern as GHCR image publish)
• Remove dead on: release trigger from cargo-publish.yml — releases created by GITHUB_TOKEN don't fire on: release events

Test plan

• Verified manually: v0.11.0 required manual workflow_dispatch to publish to crates.io
• CI passes

[Copilot]

Pull request overview

This PR updates the release automation so the crates.io publish workflow is triggered directly from the release workflow, avoiding reliance on on: release (which doesn’t fire for releases created via GITHUB_TOKEN).

Changes:

• Dispatch cargo-publish.yml from release.yml at the end of the release job.
• Remove the on: release trigger from cargo-publish.yml, leaving it workflow_dispatch-only.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/workflows/release.yml	Adds a step to trigger the crates.io publish workflow via gh workflow run on the release tag ref.
.github/workflows/cargo-publish.yml	Removes the release event trigger so publishing is driven by explicit workflow dispatch.

Comments suppressed due to low confidence (1)

.github/workflows/cargo-publish.yml:10

• With the on: release trigger removed, this workflow can no longer run in a release event context, but later steps still branch on ${{ github.event_name }} == "release" to force dry_run=false. That conditional is now unreachable and can mislead future changes; consider simplifying the workflow to always derive dry_run from inputs.dry_run (and rely on the caller—release.yml—to pass dry_run=false when publishing).

on:
  workflow_dispatch:
    inputs:
      dry_run:
        description: "Run without actually publishing"
        type: boolean
        default: true

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Linux Benchmarks

Details

Benchmark suite	Current: 1ee87eb	Previous: 682ad20	Ratio
hello_world (median)	20 ms	20 ms	1
pandas (median)	110 ms	120 ms	0.92
density (per VM)	8 MB	8 MB	1
snapshot (disk)	653 MiB	653 MiB	1

This comment was automatically generated by workflow using github-action-benchmark.

[github-actions]

Windows Benchmarks

Details

Benchmark suite	Current: 1ee87eb	Previous: 682ad20	Ratio
hello_world (median)	315 ms	291 ms	1.08
pandas (median)	977 ms	1024 ms	0.95
density (per VM)	7 MB	7 MB	1
snapshot (disk)	661 MiB	661 MiB	1

This comment was automatically generated by workflow using github-action-benchmark.