Skip to content

Conversation

@jaoleal
Copy link
Collaborator

@jaoleal jaoleal commented Dec 3, 2024

As shown by lucas here #295 (comment) , #295 could be fixed aligning the versions of cargo build and the declared version in "rust-toolchain.toml".

So i matched the version inside the justfile.

I know this changes looks strange inside the justfile and possibly will be another data to maintain if we update our MSRV.
But we need it, its the only way to certify such a external thing from our project.

Nope, not needed.

closes #295

@jaoleal jaoleal mentioned this pull request Dec 3, 2024
@jaoleal
Copy link
Collaborator Author

jaoleal commented Dec 3, 2024

cc @lucasbalieiro

@Davidson-Souza
Copy link
Member

I don't think you need to specify the toolchain version. We only had this problem because we explicitly passed a +nightly. If we just remove it then whatever is in rust-toolchainwill be respected. As per the rustup book it picks an appropriate toochain in the following steps, whichever comes first is chosen:

1 - A toolchain override shorthand used on the command-line, such as cargo +beta.
2 - The RUSTUP_TOOLCHAIN environment variable.
3 - A directory override, set with the rustup override command.
4 - The rust-toolchain.toml file.
5 - The default toolchain.

Since our justfile called with a +nightly, the first item was selected.

@jaoleal
Copy link
Collaborator Author

jaoleal commented Dec 3, 2024

Nice, thats right. I tested here and everything went well.

@Davidson-Souza
Copy link
Member

ACK 4e5715c

@Davidson-Souza Davidson-Souza merged commit 4784848 into vinteumorg:master Dec 3, 2024
6 checks passed
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 this pull request may close these issues.

Errors on test

2 participants