Repository navigation
node-process 11.3.0 from the registry, the release with loadEnvFile - #1
Merged
Merged
Conversation
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.
node-process11.3.0 is on the registry since 18 October 2026 and carriesloadEnvFile, the bindingEnv.Dotloads the.envfile. Until nowspago.yamlpinned the fork and commit of the pull request that added it(purescript-node/purescript-node-process#47).
spago.yaml: the git pin becomes the registry version, kept inextraPackagesonly because the package set still carries 11.2.0, and the dependency gets the range>=11.3.0 <12.0.0, the first with the function.README.mdandrelease.yml: the sentences saying the package could not be published while it depended on a git pin are gone; that was the one thing in the way of the registry.spago.lockfollows.