Publish to crates.io

[samcday]

So actually why not, though?

[samcday]

@codex what are the hippest Rustaceans with the twirliest beards using for release automation these days? I recall words like cargo-release and release-pleaze or somesuch?

libphosh-rs has been on crates.io for a while (thanks Guido) so I can't think of any impediments to publishing and then updating README with a "run phrog from cargo install" thing?

... hey also what about we do something to plug in to cargo binstall? I used that for Dioxus and fux wit it.

[chatgpt-codex-connector]

Summary

• Added a new README section documenting direct installation from crates.io via cargo install phrog, plus cargo binstall phrog usage and behavior. README.mdL58-L72
• Added package.metadata.binstall config in Cargo.toml so cargo-binstall can discover release archives from GitHub releases. Cargo.tomlL46-L49
• Extended the release workflow to build a release tarball (phrog-x86_64-unknown-linux-gnu.tar.gz) and attach it to GitHub releases, and added a non-RC publish-crate job that publishes to crates.io using CARGO_REGISTRY_TOKEN. .github/workflows/release.ymlL23-L52

Git / PR actions

• Committed changes on the current branch with message: release: publish crate and release tarball.
• Created a follow-up PR via make_pr:
  • Title: Follow-up: automate crates.io publishing and cargo-binstall support

Testing

• ✅ cargo fmt --all --check
• ⚠️ cargo check (fails in this environment due to missing system library metadata like glib-2.0.pc, not due to Rust syntax errors in the edited files)

View task →

[samcday]

We're publishing to crates.io since v0.53.0-rc.4. The dorky editly video even works over there you gotta love it 🙈