Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v24.3.7 of Rust crate not released to crates.io #8257

Open
snowp opened this issue Mar 13, 2024 · 4 comments · May be fixed by #8263
Open

v24.3.7 of Rust crate not released to crates.io #8257

snowp opened this issue Mar 13, 2024 · 4 comments · May be fixed by #8263

Comments

@snowp
Copy link

snowp commented Mar 13, 2024

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.

@rdelfin
Copy link

rdelfin commented Mar 16, 2024

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

@rdelfin rdelfin linked a pull request Mar 16, 2024 that will close this issue
@mkatychev
Copy link

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

@snowp
Copy link
Author

snowp commented Mar 25, 2024

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

@rdelfin
Copy link

rdelfin commented Mar 25, 2024

I've made a PR that automates the publishing to avoid this in future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants