semantic-release / github

:octocat: semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues
MIT License
402 stars 125 forks source link

RequestError when github org enabled with IP Allowlist #767

Open pavankumar-emmadi-partior opened 8 months ago

pavankumar-emmadi-partior commented 8 months ago

Current behavior

[semantic-release] › ✘ An error occurred while running semantic-release: RequestError [HttpError]: Although you appear to have the correct authorization credentials, thexxxorganization has an IP allow list enabled, and your IP address is not permitted to access this resource. at /usr/local/nvm/versions/node/v18.18.0/lib/node_modules/semantic-release/node_modules/@octokit/request/dist-node/index.js:112:21 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async requestWithGraphqlErrorHandling (/usr/local/nvm/versions/node/v18.18.0/lib/node_modules/semantic-release/node_modules/@octokit/plugin-retry/dist-node/index.js:71:20) at async Job.doExecute (/usr/local/nvm/versions/node/v18.18.0/lib/node_modules/semantic-release/node_modules/bottleneck/light.js:405:18) { status: 403,

Expected behavior

semantic-release should allow publish to the orgs with IP Allowlist enabled via proxy config. proxy: { host: 'xxxxx', port: xxx, secureProxy: true }

semantic-release version

22.0.5

CI environment

google cloudbuild

Plugins used

github

semantic-release configuration

[ "@semantic-release/github", { "assets": [ "CHANGELOG.md" ], "proxy": { "host": "xxxx", "port": xxxx, "secureProxy": true } } ]

OR

[ "@semantic-release/github", { "assets": [ "CHANGELOG.md" ], "proxy": "http://XX.XX.XX.XX:XXXX/" } ]

CI logs

[semantic-release] › ✘ An error occurred while running semantic-release: RequestError [HttpError]: Although you appear to have the correct authorization credentials, thexxxorganization has an IP allow list enabled, and your IP address is not permitted to access this resource. at /usr/local/nvm/versions/node/v18.18.0/lib/node_modules/semantic-release/node_modules/@octokit/request/dist-node/index.js:112:21 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async requestWithGraphqlErrorHandling (/usr/local/nvm/versions/node/v18.18.0/lib/node_modules/semantic-release/node_modules/@octokit/plugin-retry/dist-node/index.js:71:20) at async Job.doExecute (/usr/local/nvm/versions/node/v18.18.0/lib/node_modules/semantic-release/node_modules/bottleneck/light.js:405:18) { status: 403,

pavankumar-emmadi-partior commented 8 months ago

I believe the api requests not going through the proxy.

travi commented 8 months ago

Likely a duplicate of #696. We would welcome help with further investigation or a PR to fix/document better

vmorales-2920 commented 3 weeks ago

Facing the same issues, have you found a solution?