feat: enable use of job token for gitlab api authentication#919
feat: enable use of job token for gitlab api authentication#919fgreinacher merged 16 commits intosemantic-release:masterfrom
Conversation
There was a problem hiding this comment.
Thanks a lot @arvest-bjoneson! Please revert the formatting changes so that this is easier to review 🙇
Kind reminder to revert the formatting @arvest-bjoneson. Will help with the review. Thanks a lot for your contribution. |
|
My apologies for delay @fgreinacher @JonasSchubert - Formatting changes have been reverted! Many thanks. |
There was a problem hiding this comment.
Thanks for the update @arvest-bjoneson, this looks great! Just one remaining question from my side.
|
Hi @arvest-bjoneson @fgreinacher |
v0.10.0 has dropped support for Node.js < 22
|
@rzhornyk Thanks for the ping. I have fixed the pipeline issue. I'll go on merge this now. Thanks again for your contribution @arvest-bjoneson! |
|
🎉 This PR is included in version 13.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
I believe this change introduced a problem with releases incorrectly failing with |
The header must be a string, not an array. Per the got documentation, `headers` is of type `object<string, string>`. See https://github.com/sindresorhus/got/blob/v14.6.6/documentation/2-options.md#headers Fixes the mis-typing problem introduced in semantic-release#919 which appears to cause GitLab releases to fail with incorrect `EINVALIDGLTOKEN Invalid GitLab token.` errors
This is an implementation of recommendations made in #901