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

cargo build still compiles to 1.0.0 #2446

Open
ondohotola opened this issue Jan 16, 2025 · 2 comments
Open

cargo build still compiles to 1.0.0 #2446

ondohotola opened this issue Jan 16, 2025 · 2 comments

Comments

@ondohotola
Copy link

Tried cargo build ... on Linux and it wanted to compile to 1.0.0.

Cloned the repo
ran rustup update
ran cargo install ...

took a while (Ubuntu on a VM) but it's working :-)-O

@jqnatividad
Copy link
Collaborator

You need to issue cargo build not cargo install.

cargo install is limited to 1.0.0 as its the last published version on crates.io.

I pushed the dependency envelope a bit much with 2.0.0 and 2.1.0. 😉

In 2.0.0, I had a dependency on unreleased features in MiniJinja and cargo publish prevented me from publishing 2.0.0.

MiniJinja 2.6.0 was released with the needed features, but then I published 2.1.0 which had a dependency on another set of unreleased features in Polars (decompress and string_normalize) which prevented publishing 2.1.0 to crates.io.

You can be certain that I'll be doubly-sure 2.2.0 will only have released dependency features. 😄

@ondohotola
Copy link
Author

Thanks, I can happily live with either, but of course build needs a step or two less.

On the other hand, as Master Sergeant Farrell said in "Edge of Tomorrow :-)-O

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

No branches or pull requests

2 participants