publish.yml: add crates.io section to GitHub Release notes#364
publish.yml: add crates.io section to GitHub Release notes#364willwashburn merged 1 commit intomainfrom
Conversation
The 2.0 release body listed 11 npm packages but omitted the two crates.io publishes (relayburn-sdk@2.0.0, relayburn-cli@2.0.0) that ship in lockstep at every release. Adds a '## Crates' section right after the '## Packages' npm list, matching the structure already shown in the workflow_dispatch step summary.
|
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughRelease notes generation in the publish workflow is extended with a dedicated "Crates" section. The script now adds entries for ChangesRelease Notes Enhancement
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
The 2.0.0 release body (https://github.com/AgentWorkforce/burn/releases/tag/relayburn-v2.0.0) lists all 11 npm packages but doesn't mention the two crates.io publishes (`relayburn-sdk@2.0.0`, `relayburn-cli@2.0.0`) that ship in lockstep on every release.
Adds a `## Crates` section right after `## Packages`, with crate name, tag, and crates.io URL.
Future release bodies will look like:
The 2.0.0 release body has already shipped — happy to follow up with a `gh release edit relayburn-v2.0.0 --notes ...` to backfill it if you want, but that's a one-shot manual action and out of scope for this PR.