process.env changes not seen by subsequent steps about toolkit HOT 2 CLOSED

Yep, in general env changes from one step shouldn't affect future steps so that each action can expect its own clean environment. If you need env var changes to propogate you can use exportVariable from the core library. That should include any changes to the PATH variable - we mostly provide addPath as a convenience function to handle things like path separators in a platform agnostic way since its a common need in all of our setup actions (and other contexts)

from toolkit.

@damccorm

Thanks for pointing that out, even though I've looked at the file, I missed it. Not sure why that can't be done in the actions *.js file, as the call to exportVariable worked, but it just replaced the same code it performs.

I assume something with scoping, I'll look over the code some more...

from toolkit.