fix: sort keys in __MISE_DIFF to make the serialised value deterministic
#3640
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
jdx
reviewed
Dec 17, 2024
joshbode
force-pushed
the
sort-diff-keys
branch
from
cc49d32 to
ef7a9f0
Compare
This was referenced Dec 17, 2024
miguelmig
pushed a commit
to miguelmig/mise
that referenced
this pull request
Dec 21, 2024
…istic (jdx#3640) Co-authored-by: jdx <216188+jdx@users.noreply.github.com>
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.
__MISE_DIFFchanges value randomly when updating if any environment variablesare set by
.mise.tomlsince the keys (ofnewandold) are not being sortedwhen serialised.
(I use the value of
__MISE_DIFFto determine ifmisehas updated theenvironment to colour my prompt)