renovate[bot] on xo-0.x
chore(deps): update dependency … (compare)
semantic-release --no-ci
[16:07:15] [semantic-release] › ℹ Running semantic-release version 17.0.4
[16:07:18] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/npm"
[16:07:19] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/git"
[16:07:19] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[16:07:19] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[16:07:19] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/changelog"
[16:07:19] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/npm"
[16:07:19] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/git"
[16:07:19] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/npm"
[16:07:20] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/gitlab"
[16:07:20] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/npm"
[16:07:20] [semantic-release] › ✔ Loaded plugin "addChannel" from "@semantic-release/github"
[16:07:27] [semantic-release] › ℹ This test run was triggered on the branch development, while semantic-release is configured to only publish from master, therefore a new version won’t be published.
CI=true
variable.
Hey everyone,
I'm running into a curious issue. I'm trying to run semantic release from a gitlab runner hosted within a circle ci macos executor. I keep running into the following error:
2020-10-13T17:06:36.150Z semantic-release:get-git-auth-url Verifying ssh auth by attempting to push to https://gitlab.com/tonetechnician/repo.git
2020-10-13T17:06:36.501Z semantic-release:git Error: Command failed with exit code 128: git push --dry-run --no-verify https://gitlab.com/tonetechnician/repo.git HEAD:master
remote: You are not allowed to upload code.
fatal: unable to access 'https://gitlab.com/tonetechnician/repo.git/': The requested URL returned error: 403
at makeError (/Users/distiller/.config/yarn/global/node_modules/execa/lib/error.js:59:11)
at handlePromise (/Users/distiller/.config/yarn/global/node_modules/execa/index.js:114:26)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async verifyAuth (/Users/distiller/.config/yarn/global/node_modules/semantic-release/lib/git.js:207:5)
at async module.exports (/Users/distiller/.config/yarn/global/node_modules/semantic-release/lib/get-git-auth-url.js:47:5)
at async run (/Users/distiller/.config/yarn/global/node_modules/semantic-release/index.js:56:27)
at async module.exports (/Users/distiller/.config/yarn/global/node_modules/semantic-release/index.js:260:22)
at async module.exports (/Users/distiller/.config/yarn/global/node_modules/semantic-release/cli.js:55:5)
2020-10-13T17:06:36.501Z semantic-release:get-git-auth-url SSH key auth failed, falling back to https.
2020-10-13T17:06:39.334Z semantic-release:get-tags found tags for branch semantic-test: [ { gitTag: 'v1.0.0', version: '1.0.0', channels: [ null ] }, { gitTag: 'v1.0.1', version: '1.0.1', channels: [ null ] }, { gitTag: 'v1.0.2', version: '1.0.2', channels: [ null ] } ]
[5:06:39 PM] [semantic-release] › ℹ This test run was triggered on the branch master, while semantic-release is configured to only publish from semantic-test, therefore a new version won’t be published.
It seems as if the ssh auth is failing. What's more, is the fallback to https is also not working with no response from the package (I've also setup the GIT_CREDENTIALS environment variable with <username>:<password>). Furthermore, the git branch seems to switch to master which prevents me from being able to prepare the release (my release branch is named something different). Surely this error should cause the job to fail?
I can confirm I've setup my SSH credentials in both the gitlab runner and the circleCI executor (and also individually) by running ssh -T git@gitlab.com which lets me login correctly. I can also confirm when running the same release on my local gitlab-runner things run as expected, so I can only imagine it's something going wrong with the ssh in the CircleCI, I'm just not exactly sure what it might be.
The code in question is found here https://github.com/semantic-release/semantic-release/blob/master/lib/get-git-auth-url.js#L47