-
Notifications
You must be signed in to change notification settings - Fork 77
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
feat: add support for NO_PROXY #359
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tanks @Babbafett, I left some comments.
Also I guess you want to format the code: npm run lint -- --fix
Co-authored-by: Florian Greinacher <florian@greinacher.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking great now, thanks for your work @Babbafett!
🎉 This PR is included in version 9.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Co-authored-by: Florian Greinacher <florian@greinacher.de> Co-authored-by: Julian Beisert <julianbeisert@googlemail.com>
Please check if the MR fulfills these requirements
What kind of change does this MR introduce?
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this MR introduce a breaking change?
No
Other information
In some cases it requires a web proxy to reach resources through the internet and outside of a company network. This will work when the gitlab Instance is also accessible through the internet, but in some cases the gitlab instance is a self hosted one and is only be reachable within the same network.
In case of that you need a proxy configuration (e.g. through HTTP_PROXY and/or HTTPS_PROXY for your build process with @semantic-release/exec) it would fail to reach the gitlab instance as a combination of proxy and no_proxy is not possible at the moment.
This PR will introduce this option to allow a combination of having HTTP_PROXY/HTTPS_PROXY and NO_PROXY environment variables