Repository navigation
chore(release): bump to 0.5.0 and document breaking changes - #195
Merged
Merged
Conversation
13 PRs since v0.3.0: stable cross-language error model (one opaque aimux_error_t* + unified code space), request pipeline aligned with the AI SDK (core-owned retries/timeouts/stream lifecycle, video start/status split), tool inputs parsed and validated at the Core boundary with host-side repair in every binding, WS proxy tunnel + ElevenLabs scribe_v2_realtime, SSRF hardening for provider-supplied download URLs. Version bumps: workspace Cargo.toml (+4 path deps), Node package.json/ lock, Python pyproject.toml + Cargo.toml (0.2.0, realigned), Java, Kotlin, Flutter pubspec, web-console package.json/lock.
…_chunks Mirrors trace/hash.rs: the bare allow is itself an unknown lint under rustc < 1.98, which fails the pre-push clippy gate on stable 1.97.
The committed index.js is a napi build artifact; its requireNative platform-package version checks embed the package version, so the CI 'committed copies match napi output' gate fails after the bump. Regenerated with napi build; index.d.ts is unchanged.
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.
Summary
Release prep for v0.5.0 — 13 PRs since v0.3.0, skipping 0.4.0 per release decision.
Since v0.3.0 the surface changed in three breaking areas:
aimux_error_t *on the C ABI, unified code space (AiMuxError 1–17, RecordingError 100–105, C-boundary 200–206); Node/Python throw native typed exceptions.ToolCall.inputisString), host-siderepairToolCallin all eight bindings (RFC-0035).Plus: WS proxy tunnel + ElevenLabs
scribe_v2_realtime(RFC-0034), SSRF hardening for provider-supplied download URLs (#163), Go lifecycle deadlock fixes (#157), and the CI fixes for the console-build matrix that kept aimux-web/aimux-cli/aimux-replay out of the v0.3.0 artifacts (#155/#156).Changes
[0.5.0] - 2026-09-27entry (Breaking/Added/Changed/Fixed/Removed, mirroring the 0.3.0 structure) + link refs.Cargo.toml(+4 internal path deps), Node package.json/lock, Python pyproject.toml and Cargo.toml (was stale at 0.2.0 — realigned), Java + Kotlin gradle, Flutter pubspec, web-console package.json/lock.openai/embedding.rsallow gainsunknown_lints(mirrorstrace/hash.rs) — the 1.98-only lint name fails the pre-push gate on stable 1.97.Validation
cargo check --workspaceclean;cargo clippy --workspace --all-targetszero warnings (pre-commit/pre-push hooks pass).0.3.0/0.2.0outside CHANGELOG history andreference/third-party code.v0.5.0after merge drives crates.io/npm/PyPI/Maven/pub.dev/GitHub Release.Release notes entry
See the full 0.5.0 CHANGELOG section.