-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance documentation/ explain how it works #52
Comments
Yep!
Yes, it does. This is somewhat intentional, as I'm not sure where the package.json would be reversed. During the full run of the workflow (I suppose until the next run of the volta-cli/action action again) the node/yarn/npm versions specified in the actions config should "override" whatever happens to be in |
I think this is a feature request for volta instead: Support running temporary node versions |
Hmm, I think this already exists.
|
But it's not suitable for this action for example. It would be something like:
|
I guess I don't understand what you are asking for. Currently we support two main modes of operation:
What sort of timing / lifetime are you looking for? |
I'm just looking for something that could be used by this |
Why does the mutation of package.json matter in your case? Is there something that the current |
I use In my case, I'm safe, since I don't call Nonetheless, I can think of 2 cases where this would break:
Side note: I'm now thinking about doing this deliberately, so I can keep my References volta-cli/volta#905. |
Thanks for the explanation! I'm not sure there is a reasonable solution we can do here though. I can't think of a good heuristic that would allow us to reset that wouldn't also be annoying for non-release cases. |
I thought in something like:
If you'd like, I can move this discussion to the main volta repo. But for this repo, I think the current behavior should be documented, so the users would be at least aware of the |
Yes, sounds good to me. |
RE: the volta internals, I think we'd need volta-cli/volta#282 to be resolved to avoid mutating |
Going to close this issue for now (thank you for the awesome conversation though @felipecrs), as it seems like a more general feature request over in volta itself. |
I wonder how it suppresses the
node
version I've set in mypackage.json
, which is a very good feature, but I wonder how this action does that.Is it by running
volta pin node@version
? If so, does it leave thepackage.json
modified?The text was updated successfully, but these errors were encountered: