You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During verification process, when facing SSL problems, the following Error occurs:
TypeError: Cannot read property 'statusCode' of undefined
at module.exports (/builds/....../test-ci-semantic-release/node_modules/@semantic-release/gitlab/lib/verify.js:65:26)
at processTicksAndRejections (node:internal/process/task_queues:94:5)
at async verifyConditions (/builds/....../test-ci-semantic-release/node_modules/@semantic-release/gitlab/index.js:9:3)
at async validator (/builds/....../test-ci-semantic-release/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
at async /builds/....../test-ci-semantic-release/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
at async Promise.all (index 0)
at async next (/builds/....../test-ci-semantic-release/node_modules/p-reduce/index.js:16:18) {
pluginName: '@semantic-release/gitlab'
}
Expected behavior
The Error handling in line 62 of verify.js is broken. It expects error.response to be always defined, which is not the case.
The catch block should not cause its own error, making the original error, which occured (i.e. due to our SSL issue), inaccessible.
Simple solution would be to just throw the error, when error.response is undefined. This is at least how we debugged this ourselves.
TypeError: Cannot read property 'statusCode' of undefined
at module.exports (/builds/....../test-ci-semantic-release/node_modules/@semantic-release/gitlab/lib/verify.js:65:26)
at processTicksAndRejections (node:internal/process/task_queues:94:5)
at async verifyConditions (/builds/....../test-ci-semantic-release/node_modules/@semantic-release/gitlab/index.js:9:3)
at async validator (/builds/....../test-ci-semantic-release/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
at async /builds/....../test-ci-semantic-release/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
at async Promise.all (index 0)
at async next (/builds/....../test-ci-semantic-release/node_modules/p-reduce/index.js:16:18) {
pluginName: '@semantic-release/gitlab'
}
The text was updated successfully, but these errors were encountered:
Current behavior
During verification process, when facing SSL problems, the following Error occurs:
Expected behavior
The Error handling in
line 62
of verify.js is broken. It expectserror.response
to be always defined, which is not the case.The catch block should not cause its own error, making the original error, which occured (i.e. due to our SSL issue), inaccessible.
Simple solution would be to just throw the error, when
error.response
is undefined. This is at least how we debugged this ourselves.Environment
The text was updated successfully, but these errors were encountered: