semantic-release / semantic-release/github
RequestError when github org enabled with IP Allowlist
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
Current behavior
[semantic-release] › ✘ An error occurred while running semantic-release: RequestError [HttpError]: Although you appear to have the correct authorization credentials, thexxx organization 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, thexxx organization 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,
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Start by reproducing the GitHub publish with the shown proxy configurations and inspect how the plugin constructs its GitHub requests; done means publishing succeeds for an organization whose IP allowlist requires the proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- release, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100