Replies: 18 comments 50 replies
-
|
my plan:
(example for if |
Beta Was this translation helpful? Give feedback.
-
|
Is |
Beta Was this translation helpful? Give feedback.
-
|
One scenario where having this on by default is helpful would be doing a migration from idiomatic version files to Would the |
Beta Was this translation helpful? Give feedback.
-
|
One thing I'm conscious of is that people might want to do this in specific projects: [settings]
idiomatic_version_file_enable_tools = ["node"]to have a One solution to this would be to make the tool part of the setting key: [python]
idiomatic_version_file = truehowever there isn't really a way to have fully dynamic settings right now for non-core tools. |
Beta Was this translation helpful? Give feedback.
-
|
I don't fully understand the implications of this. I'm seeing the warning in a project with a |
Beta Was this translation helpful? Give feedback.
-
|
I am new to mise but would prefer not to have ruby installed just because there's a Gemfile in a directory. This is primarily because I run everything in containers, but even if I was still using rvm I don't think I'd want it. I am also not in love with having the deprecation show up at all. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I want to ask if it's disabled by default, will mise still automatically switch to the Ruby version specified in .ruby-version when I enter the directory, or does it simply not get installed automatically? |
Beta Was this translation helpful? Give feedback.
-
|
This poll is closed and was unanimous in favor of making this breaking change when the deprecation message was added. As a general rule, I do not make breaking changes in mise. This is a rare exception for reasons stated above. If you're new to mise and don't understand any of this, just run If you rely on idiomatic version files, you'll need to run |
Beta Was this translation helpful? Give feedback.
-
|
I know I'm a little late to this discussion and I absolutely not only respect the logic around this change but even agree with it! However, I think the benefit of supporting idiomatic version files when migrating from other tools makes Another specific use case for me (and a reason why I plan on setting the Do you think there might be a middle ground here, where plain version files like |
Beta Was this translation helpful? Give feedback.
-
|
As a brand new
|
Beta Was this translation helpful? Give feedback.
-
|
I had the same experience. The verbatim command would have solved the
problem for me.
…On Wed, Apr 23, 2025 at 2:25 PM John Hume ***@***.***> wrote:
As a brand new mise user, not knowing to use ruby for the <TOOL>
mentioned in the below message was a speedbump, leading to a web search and
this thread. It would be sweet if it gave the verbatim command needed for
the tool whose idiomatic version file triggered the warning.
mise WARN deprecated [idiomatic_version_file_enable_tools]: idiomatic
version files like ~/src/web/Gemfile are currently enabled by default
however this will change in mise 2025.10.0 to instead default to disabled.
You can remove this warning by explicitly enabling idiomatic version files
for with mise settings add idiomatic_version_file_enable_tools <TOOL>.
See #4345 <#4345> for more
information.
—
Reply to this email directly, view it on GitHub
<#4345 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACC5COQWD2C4WI4KKJXRL23AALNAVCNFSM6AAAAABWXVUXSSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJSG43TOMY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Should the deprecation message be shown even when the setting is configured? Also, it is probably a good ideia to have all available |
Beta Was this translation helpful? Give feedback.
-
@jdx is this the main / sole reason for this change? It makes me wonder if you are thinking of dropping support for idiomatic version files in the future. Also, related but a bit tangential, is there some other setting that would "cause mise to install that tool", or are you simply referring to the behaviour resulting from running |
Beta Was this translation helpful? Give feedback.
-
|
Just wanted to applaud this decision -- I work at a company where some repos have adopted |
Beta Was this translation helpful? Give feedback.
-
|
One thought I had around this was perhaps we could configure based on filename instead of tool name, e.g.: It'd be quite a bit more challenging to implement but I think it's possible. It'd be easier once the old logic is sunset. One issue with this approach might be if 2 different tools had the same filename—though I don't think any standard setup would have this. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe mise could produce a warning by default when all of the following conditions are true:
Because it would just be a warning, this wouldn't be a breaking change when new idiomatic version files are introduced. It also wouldn't be very intrusive, since the warning would only appear if mise is currently managing the tool in question and there's a mismatch between the version chosen by mise and the idiomatic version file. |
Beta Was this translation helpful? Give feedback.
-
|
It seems like version files are being conflated with project files. Gemfile present: new default makes sense, don't install Ruby unless asked. |
Beta Was this translation helpful? Give feedback.
-
|
Any way to suppress this message on every new terminal? mise WARN unknown field in ~/.config/mise/config.toml: settings.idiomatic_version_file_enable_tools
mise WARN unknown field in ~/.config/mise/config.toml: settings.idiomatic_version_file_enable_tools
mise WARN unknown field in ~/.config/mise/config.toml: settings.idiomatic_version_file_enable_tools
~
❯ cat ~/.config/mise/config.toml
[settings]
idiomatic_version_file_enable_tools = []
❯ mise version
_ __
____ ___ (_)_______ ___ ____ ____ / /___ _________
/ __ `__ \/ / ___/ _ \______/ _ \/ __ \______/ __ \/ / __ `/ ___/ _ \
/ / / / / / (__ ) __/_____/ __/ / / /_____/ /_/ / / /_/ / /__/ __/
/_/ /_/ /_/_/____/\___/ \___/_/ /_/ / .___/_/\__,_/\___/\___/
/_/ by @jdx
2025.5.3 macos-arm64 (2025-05-09) |
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am starting to feel that idiomatic versions should default to disabled and enabled via settings for specific tools. I think back when mise started defaulting to enabled made sense because each language required a plugin. Now that most of the tools with idiomatic versions are core, it's weird that just having a
go.modorGemfilein the project directory causes mise to install that tool.While it's certainly convenient that mise works with everything out of the box, I think it's too much and before these files should be used a command like
mise settings add idiomatic_version_file_enable_tools ruby.This is, of course, a breaking change. My plan to roll it out is to show a warning when an idiomatic version file is in use and the setting is not set for 6 months.
I'll leave this open for 30 days and go with whatever people think is best.
0 votes ·
Beta Was this translation helpful? Give feedback.
All reactions