fix: deprecate direnv integration #3464
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this is not a new decision, this simply documents what has been the actual state of the world for a long time.
If people are still using and liking
use miseI wouldn't worry, it hasn't had any real changes in a very long time so likely will continue humming along as it does today. I'm probably willing to accept PRs for it too, so it's kind of a "soft" deprecation. I won't be maintaining it myself though so this makes that position clear.And using direnv with mise together is something I'm going to be more explicit about not supporting. mise may have some lagging feature parity gaps with direnv but I don't think there are very many and certainly not many that are heavily used.