Release v2.0.0 - #257
Merged
Merged
Release v2.0.0#257
Conversation
…es and new features
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the v2.0.0 release: version bumps, changelog roll-up, release notes, and a dependency cleanup. Opened so CI can show the current state before tagging.
Why 2.0.0
The
Unreleasedsection carried five explicitly breaking subsections across 119 commits since v1.1.0. The decisive one is the wire break:PROTOCOL_VERSIONmoves"2.0"→"3.0"andhellonow negotiates it, so a pre-3.x client is refused at the handshake rather than failing on its first call. Combined withaimdb-ws-protocolbeing deleted,AimDbBuilder::with_remote_accessremoved, the runtime genericRdropped from core's object graph, and.replacing/as the topic separator, this is a major release.Versions
Every number below was checked against
index.crates.io— none collide with a published version, and the three new connector names are unregistered.aimdb-coreaimdb-persistenceaimdb-deriveaimdb-persistence-sqliteaimdb-data-contractsaimdb-mqtt-connectoraimdb-clientaimdb-knx-connectoraimdb-codegenaimdb-websocket-connectoraimdb-embassy-adapteraimdb-wasm-adapteraimdb-tokio-adapteraimdb-cliaimdb-syncaimdb-mcpNew, first publish:
aimdb-uds-connector,aimdb-serial-connector,aimdb-tcp-connector— all0.1.0.Six crates carried in-flight bumps that were never published (
aimdb-core1.2.0,aimdb-derive0.3.0,aimdb-data-contracts0.4.0 among them). Since nothing was burned on crates.io, these were reset to what the changelogs actually justify rather than left overshooting — soaimdb-deriveships 0.2.0, not 0.3.0. All 32 internal dependency pins were updated to match.Changelogs
All 20 rolled to
[<version>] - 2026-09-18, with an empty[Unreleased]left on top. Two stale link refs were dropped —aimdb-core's[1.2.0]andaimdb-sync's[0.6.0]— both pre-added for versions that were never released.New
docs/releases/v2.0.0.mdcovers the breaking changes and a seven-step migration guide.Dependency cleanup
cargo-machetefound nine unused dependencies; eight are removed here:aimdb-core:anyhow— dead since design 038 deletedinto_anyhow(), its last consumeraimdb-tokio-adapter:dep:tracing— the design 050 sweep missed this one; now matchesaimdb-uds-connector's formaimdb-mcp: theaimdb-coredependency — unused, and itsstd/observabilityfeatures already arrive viaaimdb-clientaimdb-embassy-adapter,aimdb-mqtt-connector:futures-core(non-optional, so it built for every consumer)aimdb-mqtt-connector:thiserror,async-stream,futures-util— these were listed in thestdfeature, so every std build compiled all threerand_coreinaimdb-mqtt-connectoris held back pending a check on theembedded-tlsleg:CryptoRngCorecomes fromembedded_tls, notrand_core, but it may still matter for version unification.Four machete hits are intentional and left alone —
critical-sectionin the tcp/knx/mqtt connectors (linked by symbol name forCriticalSectionRawMutex) anddefmtin the serial connector (referenced by macro expansion at the invocation site). All four are already documented in their manifests.Verification
Local checks after the removals, all passing:
CI covers the full feature matrix from here.
Known issues, not addressed
aimdb-core1.0.1 is published but has no changelog entry — the file jumps 1.0.0 → 1.1.0.aimdb-mcp-v0.8.0point at tags that were never created. New refs in this PR use thev2.0.0workspace tag, the only one this release will produce.aimdb-executor0.2.0 andaimdb-ws-protocol0.1.0 stay published but are gone from the workspace; the release notes mark them retired.Before merging
Cargo.lockis included and in sync. After merge: tagv2.0.0, thenmake publishwalks the 19 crates in dependency order.🤖 Generated with Claude Code