Repository navigation
Version Packages - #4
Merged
Merged
Conversation
Closed
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
fnm@1.40.0
Minor Changes
29d9a38Thanks @christophersarmiento! - AddFNM_AUTH_HEADERenv variable. When set, its value is forwarded verbatim as theAuthorizationHTTP header on requests to the Node.js dist mirror, enabling fnm to work with private/auth-protected mirrors.Patch Changes
#1529
b24c183Thanks @Schniz! - the title of the change in a few words.If necessary, you can add examples, links to related issues, or any other information that would be helpful for the maintainers and users of the project:
#1361
168e51fThanks @kaaax0815! - supportx64-glibc-217arch by adding a--arch x64-glibc-217to fnm env#1525
bfb1860Thanks @Schniz! - prefer explicit shell flags in installer-generated shell setup and fix ARM installer CI platform selection#1523
dc8c54aThanks @Schniz! - Clarify the interactivefnm usemissing-version prompt by prefixing the message withfnmso it is obvious which tool is asking to install Node.74f94beThanks @christophersarmiento! - Fix a flakyFNM_AUTH_HEADERe2e test. The proxy server tracked the last observedAuthorizationheader in a single global variable, which parallel test workers clobbered. Auth headers are now recorded per-test via a unique mirror path prefix.#1529
b24c183Thanks @Schniz! - Document contributor guidance for e2e tests and changesets inAGENTS.md.74f94beThanks @christophersarmiento! - Add arelease binariesGitHub Actions workflow that builds the per-platform binaries and publishes them asfnm-<platform>.zipassets on a GitHub Release when a tag is pushed. Remove therelease to cargoworkflow, as releases are published only via GitHub Releases.2aacfbcThanks @christophersarmiento! - Grant thereleaseworkflowcontents: writeandpull-requests: writepermissions so the changesets action can push the "Version Packages" branch and open its PR.#1536
a53186dThanks @joliss! - Add random number to multishell symlinks to avoid clashing#1533
b3d190bThanks @theborowski! - feat: add possible values to the arch help docs.