Skip to content

release: prep 0.8.1 (ramqp-core 0.2.4 + ramqp 0.8.1) - #25

Merged
mack42 merged 1 commit into
mainfrom
release/v0.8.1
Jul 13, 2026
Merged

release: prep 0.8.1 (ramqp-core 0.2.4 + ramqp 0.8.1)#25
mack42 merged 1 commit into
mainfrom
release/v0.8.1

Conversation

@mack42

@mack42 mack42 commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Pre-release housekeeping for the first workspace publish (ramqp-core 0.2.4 + ramqp 0.8.1). No code changes — manifests and docs only.

Changes

  • CHANGELOG: stamp the 0.8.0 and 0.8.1 headings with today's date (2026-07-13).
  • Version pin sync: ramqp's ramqp-core pin 0.2.10.2.4 (RELEASING.md §34; publish worked either way via ^0.2.1, but keep it honest).
  • README: refresh the crate-status table to ramqp-core 0.2.4 / ramqp 0.8.1.
  • ramqp-broker publish = false: held back (pre-alpha; RELEASING.md Option A) so it can't be published by accident.

Pre-publish gates (all green on this branch)

  • cargo clippy --all-targets --all-features -- -D warnings — clean
  • cargo test --all-features — ~290 tests pass, 0 failed (7 live-broker interop ignored)
  • cargo publish -p ramqp-core --dry-run — packages OK (47 files, 90.5 KiB)
  • ramqp public API unchanged, compile-locked by tests/public_api.rs

After merge

Tag v0.8.1 on main and push it — release.yml publishes ramqp-core then ramqp, then cuts the GitHub release.

- Date CHANGELOG 0.8.0 and 0.8.1 headings (2026-07-13)
- Sync ramqp's ramqp-core pin 0.2.1 -> 0.2.4
- Refresh README crate-status version strings to 0.2.4 / 0.8.1
- Guard ramqp-broker with publish = false (pre-alpha, held back)
@mack42 mack42 self-assigned this Jul 13, 2026
@mack42
mack42 merged commit 74c6caa into main Jul 13, 2026
8 checks passed
@mack42
mack42 deleted the release/v0.8.1 branch July 13, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant