fix: switch go-tools' own npm backend off aube, unblock npm:renovate - #51
Merged
Conversation
Fresh CI runners default mise's npm backend to aube, whose trust-downgrade guard currently blocks npm:renovate via a transitive dependency: @yarnpkg/libzip@3.2.2 dropped npm provenance attestation that 3.2.0/3.2.1 had. This is unrelated to which renovate version we pin (confirmed by testing) and outside our control - it could stay broken indefinitely. Pin [settings.npm] package_manager = "npm" for this repo's own tool installs. The Copier template (template/mise.toml.jinja) keeps aube's default for consumer repos - that's about catching regressions in tools *we* pin directly (like npm:cpd), a different tradeoff than a CLI's own uncontrollable transitive dependency tree.
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
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.
Summary
Fresh CI runners default mise's npm backend to
aube, whose trust-downgrade guard currently blocksnpm:renovatevia a transitive dependency:@yarnpkg/libzip@3.2.2dropped npm provenance attestation that3.2.0/3.2.1had (confirmed directly against aube:ERR_AUBE_TRUST_DOWNGRADE). This is unrelated to whichrenovateversion we pin and outside our control - it could stay broken indefinitely upstream.Pins
[settings.npm] package_manager = "npm"for this repo's own tool installs to unblock it.template/mise.toml.jinja(the Copier template consumer repos render) keeps aube's default - that's about catching regressions in tools we pin directly (likenpm:cpd, see #50), a different tradeoff than a CLI's own uncontrollable transitive dependency tree.Independent of #49/#50 - based directly on
main.Test plan
mise install npm:renovatesucceeds locally with this settinghk check --allpasses