Fix mise in CI using wrong NPM backend - #739
Merged
Merged
Conversation
austin-autify
force-pushed
the
austin-autify/fix-mise-lock
branch
2 times, most recently
from
August 27, 2026 00:54
d08f26e to
5f4c736
Compare
xiankai
approved these changes
Aug 27, 2026
austin-autify
force-pushed
the
austin-autify/fix-mise-lock
branch
from
August 27, 2026 01:48
5f4c736 to
73ee338
Compare
xiankai
approved these changes
Aug 27, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Regenerated the lockfile in order to use the aqua backend on Linux/macOS and the
npm:npmbackend on Windows which should clear the CI errors and use npm 11 everywhere. Also added some guards for this inpackage.jsonand.npmrc