Minor versions do not support backwards compatibility

[MatthewLM]

Describe the bug

If the package version is specified using a caret in pubspec.yaml and the minor version is updated, an error will be produced similar to:

Bad state: flutter_rust_bridge's codegen version (2.6.0) should be the same as runtime version (2.7.0)

Minor version numbers should allow backwards compatibility if semantic versioning is followed.

Steps to reproduce

Self evident

Logs

No need for logs

Expected behavior

No response

Generated binding code

No response

OS

No response

Version of flutter_rust_bridge_codegen

No response

Flutter info

No response

Version of clang++

No response

Additional context

No response

[fzyzcjy]

It supports backward compatibility in the sense that, the user code should be able to run when upgrading from 2.6.0 to 2.7.0 without issues.

For your question, it is that you need to keep Rust flutter_rust_bridge in sync with Dart flutter_rust_bridge version. This is usually automatically done when running flutter_rust_bridge_codegen.