Releases: fzyzcjy/flutter_rust_bridge
Releases · fzyzcjy/flutter_rust_bridge
v2.0.0-dev.7
- Please refer to https://fzyzcjy.github.io/flutter_rust_bridge/guides/miscellaneous/whats-new for what's changed in V2.
- Improve error message when a file ending is not provided in configuration #1540 (thanks @patmuk)
v2.0.0-dev.6
- Please refer to https://fzyzcjy.github.io/flutter_rust_bridge/guides/miscellaneous/whats-new for what's changed in V2.
- Remove double-allocation for enum CST decode #1500 (thanks @Desdaemon)
v2.0.0-dev.5
- Please refer to https://fzyzcjy.github.io/flutter_rust_bridge/guides/miscellaneous/whats-new for what's changed in V2.
- Set the msrv #1463 (thanks @patmuk)
- Toggle off default
clap
feature forcbindgen
#1503 (thanks @CosmicHorrorDev)
v2.0.0-dev.4
- Please refer to https://fzyzcjy.github.io/flutter_rust_bridge/guides/miscellaneous/whats-new for what's changed in V2.
- Fix Generated Rust code of
Result<RustOpaque<...>>
is incorrect #1474 (thanks @trobanga) - (My (@fzyzcjy's) PRs are not listed here)
v2.0.0-dev.3
- Please refer to https://fzyzcjy.github.io/flutter_rust_bridge/guides/miscellaneous/whats-new for what's changed in V2.
- This is still a separate version to see whether the readme image layout works for pub.dev and crates.io.
v2.0.0-dev.2
- Please refer to https://fzyzcjy.github.io/flutter_rust_bridge/guides/miscellaneous/whats-new for what's changed in V2.
- This is again a separate version, because I need to trigger the
release
CI to fix the binary forcargo binstall
(that CI did not checkout recursive submodule before).
v2.0.0-dev.1
- Please refer to https://fzyzcjy.github.io/flutter_rust_bridge/guides/miscellaneous/whats-new for what's changed in V2.
- This is a separate version, because cargo publish seems not to understand frb_codegen's template Cargo.toml files, so need to publish version to test.
v2.0.0-dev.0
- Please refer to https://fzyzcjy.github.io/flutter_rust_bridge/guides/miscellaneous/whats-new for what's changed in V2.
- The 2.0.0-dev.0 will contain bugs and missing features, because I have to have a real (pre-)release before I can start working on the last part of tests and functionalities. So it is a chicken-and-egg problem ;) But I expect 2.0.0-dev.2 (or -dev.3) to be stable.