Skip to content

Comments

make manifestversiondetect config default to true#1410

Open
KristofferC wants to merge 1 commit intoJuliaLang:mainfrom
KristofferC:kc/version_detect_true
Open

make manifestversiondetect config default to true#1410
KristofferC wants to merge 1 commit intoJuliaLang:mainfrom
KristofferC:kc/version_detect_true

Conversation

@KristofferC
Copy link
Member

This is working quite nicely for me at least.

@visr
Copy link
Contributor

visr commented Feb 5, 2026

I support defaulting to true after having used it for a while.
However when a new patch release comes out, I don't like that I have to override this for each project to avoid staying on older patch releases.
Would it be an idea to start the latest patch release that is installed, as long as it isn't older than the version in the manifest? There are cases where you don't want this, but I suspect they are far fewer.

@IanButterworth
Copy link
Member

I think we might want to notify of this behavior change when juliaup updates itself, which is currently silent.

@IanButterworth
Copy link
Member

Proposal for that notification system here #1411

@KristofferC
Copy link
Member Author

Would it be an idea to start the latest patch release that is installed, as long as it isn't older than the version in the manifest?

I'm not sure I would want that. You need to recompile your environment, etc. Part of the niceness of this is, imo, that things kind of keep working the way they did. And if you want to force a specific julia version, you can use JULIAUP_CHANNEL maybe?

@visr
Copy link
Contributor

visr commented Feb 6, 2026

things kind of keep working the way they did

From the priority list I think people mostly rely on the last one, the default channel. This comes above the default channel, so it does change things. The default channel tends to move with the patch releases and not keep older patch releases installed.

I expect people will start running into this a lot:

❯ julia
Question: The Juliaup channel '1.12.3' is not installed. Would you like to install it?: No
ERROR: `1.12.3` resolved from project manifest is not installed. Please run `juliaup add 1.12.3` to install channel or version.

So we'd suggest them to install and hence keep using an older patch release, even though in practice we'd recommend julia +1.12 --project -e 'using Pkg; Pkg.resolve()', after which it will select the latest 1.12 again.

I appreciate that the current approach is simpler, but I'm afraid it will cause people to run behind on julia patches, and/or use different patch releases at the same time without intending to. But perhaps that is the difficulty of equating the julia version the manifest last got resolved with, with the version that we want people to use by default.

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.

3 participants