-
Notifications
You must be signed in to change notification settings - Fork 26
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
Passing enviornment variables to the script #160
Comments
see #117 for a possible solution; endorse that if it’s what you needed. (it’s taking sooooo much time to assess that by the author, though! 😣) |
I had the same problem, and after some trial and error I noticed that I could simply access the environment through the process object. Adapting your example, it would look like this:
It would still be nice to see #117 merged into master though. |
this should work if you use the method you’ve indicated should almost certainly fail (as far as i remember) if you’ve settled for |
@pvdlg bumping! |
The most recent release job failed; I suspect this happened due to this issue in `semantic-release/exec`: semantic-release/exec#160 This follows a suggestion in that issue to read the necessary variable from `process.env` in an attempt to fix package publishing.
Since it is not possible to pass environment variables to process spawned by the [semantic-release-exec-plugin](https://github.com/semantic-release/exec), move publishing artifacts into an seperate process that runs after a release is made. For more details regarding this issue, see [here](semantic-release/exec#160).
Since it is impossible to pass environment variables to processes spawned by the [semantic-release-exec-plugin](https://github.com/semantic-release/exec), move publishing artifacts into an seperate process that runs after a release is made. For more details regarding this issue, see [here](semantic-release/exec#160).
Since it is impossible to pass environment variables to processes spawned by the [semantic-release-exec-plugin](https://github.com/semantic-release/exec), move publishing artifacts into an seperate process that runs after a release is made. For more details regarding this issue, see [here](semantic-release/exec#160).
My "publishCmd" script needs environment variables to be set to run properly.
How could I pass them to the script?
I've tried the code below but with no success:
The text was updated successfully, but these errors were encountered: