Closed snowp closed 1 month ago
I'm surprised this isn't at least a minor version bump. More generally, is there a compatibility mapping maintained between CLI versions and rust library versions? Building in lockstep does help but is cumbersome if you're using crates.io
This is a pretty big issue for my org as the we currently cannot use the latest flatc
since the codegen is a breaking change
For a workaround for anyone blocked on this I ended up doing this
flatbuffers = { git = "https://github.com/google/flatbuffers", tag = "v24.3.7" }
which has unblocked us for now
I've made a PR that automates the publishing to avoid this in future
It looks like a new crate version has already been published (v24.3.25). I also see one of the crate owners is a github bot too. @CasperN / @rw / @dbaileychess I assume this can be closed? Thanks for resolving this!
Seems like v24.3.7 was released not too long ago which generates code incompatible with the most recently available version of the Rust library available via crates.io (v23.5.26).
For now I've unblocked myself by depending on the GH repo directly @ the latest released tag, but it would be nice to have the most recent version of the lib available in crates.io.