Skip to content

Release rodbus 1.6.0-M2 (crates.io only) - #192

Merged
jadamcrain merged 1 commit into
mainfrom
release/1.6.0-M2
Aug 8, 2026
Merged

Release rodbus 1.6.0-M2 (crates.io only)#192
jadamcrain merged 1 commit into
mainfrom
release/1.6.0-M2

Conversation

@jadamcrain

Copy link
Copy Markdown
Member

Milestone release for #191. No FFI changes, so this is not pushed to Maven/NuGet/docs.

Lockstep version bump across all crates, FFI binding build files, and the guide. The lockstep bump is required even for a crates.io-only publish: rodbus-schema asserts the bindings' expected version against rodbus::VERSION, so bumping rodbus alone fails the binding tests.

After merge, publish manually from main with cargo publish -p rodbus. No tag is pushed — a tag would fire the full release pipeline across every ecosystem.

Milestone to publish only the `rodbus` crate to crates.io for the shared
client channel access change (#191). There are no FFI changes, so this
milestone is not pushed to Maven/NuGet/docs.

Full lockstep version bump 1.6.0-M1 -> 1.6.0-M2 across all crates, FFI
binding build files, and the guide. The lockstep bump is required even
for a crates.io-only publish: the FFI layer asserts the generated
bindings' expected version (rodbus-schema, ffi/rodbus-schema/src/lib.rs)
against the native library's runtime version (rodbus::VERSION, via
ffi/rodbus-ffi/src/lib.rs), so bumping rodbus alone fails the binding
tests in CI.

Release process: this does NOT use the tag-driven pipeline (a tag fires
all release jobs across every ecosystem). After merge, publish manually
from main with `cargo publish -p rodbus`; no git tag is pushed. Binding
versions therefore read 1.6.0-M2 in source but stay published at 1.5.0
until the 1.6.0 final re-syncs everything.
@jadamcrain
jadamcrain merged commit 2470df0 into main Aug 8, 2026
30 checks passed
@jadamcrain
jadamcrain deleted the release/1.6.0-M2 branch August 8, 2026 03:01
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