Not Found on gitlab 14.1.0 #263
Comments
|
It was due to the old version library. I was using 6.0.4, upgrading to 6.2.1 resolved the issue. (self close) |
EvanCarroll
added a commit
to EvanCarroll/gitlab
that referenced
this issue
Jul 29, 2021
Previously GitLab lables were just the basename for files uploaded as
part of the release. This is problematic because GitLab doesn't allow
conflicting labels -- a condition that could be caused by uploading a
release with two files by the same name in different directories. This
would generate a 409 Conflict error.
This patches changes the labels for files uploaded as part of a release
to the name relative to pkgRoot, or the package.
A project may look like this
pkg
pkg \ foo \ baz
pkg \ bar \ baz
This used to creating two conflicting labels of 'baz'. Now you would
have {"foo/baz", "bar/baz"} with no conflict.
GitHub issues: semantic-release#263, semantic-release#158
EvanCarroll
added a commit
to EvanCarroll/gitlab
that referenced
this issue
Jul 29, 2021
Previously GitLab lables were just the basename for files uploaded as
part of the release. This is problematic because GitLab doesn't allow
conflicting labels -- a condition that could be caused by uploading a
release with two files by the same name in different directories. This
would generate a 409 Conflict error.
This patches changes the labels for files uploaded as part of a release
to the name relative to pkgRoot, or the package.
A project may look like this
pkg
pkg \ foo \ baz
pkg \ bar \ baz
This used to creating two conflicting labels of 'baz'. Now you would
have {"foo/baz", "bar/baz"} with no conflict.
GitHub issues: semantic-release#263, semantic-release#158
EvanCarroll
added a commit
to EvanCarroll/gitlab
that referenced
this issue
Jul 29, 2021
Previously GitLab lables were just the basename for files uploaded as
part of the release. This is problematic because GitLab doesn't allow
conflicting labels -- a condition that could be caused by uploading a
release with two files by the same name in different directories. This
would generate a 409 Conflict error.
This patches changes the labels for files uploaded as part of a release
to the name relative to pkgRoot, or the package.
A project may look like this
pkg
pkg \ foo \ baz
pkg \ bar \ baz
This used to creating two conflicting labels of 'baz'. Now you would
have {"foo/baz", "bar/baz"} with no conflict.
GitHub issues: semantic-release#263, semantic-release#158
EvanCarroll
added a commit
to EvanCarroll/gitlab
that referenced
this issue
Jul 29, 2021
Previously GitLab lables were just the basename for files uploaded as
part of the release. This is problematic because GitLab doesn't allow
conflicting labels -- a condition that could be caused by uploading a
release with two files by the same name in different directories. This
would generate a 409 Conflict error.
This changes the labels for files uploaded as part of a release to the
name relative to pkgRoot, or the package.
A project may look like this
pkg
pkg \ foo \ baz
pkg \ bar \ baz
This would previously result in two conflicting labels of 'baz'. Now you
would have {"foo/baz", "bar/baz"} with no conflict.
GitHub issues: semantic-release#263, semantic-release#158
Which library? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I updated gitlab to community 14.1.0 lately, and running semantic-release failed.
semantic-release/gitlab could uploads the file like version.txt, and changelog, but after that, the job is failed due to "Not Found" error.
Below is the logs from --debug
[Logs]
[8:53:39 PM] [semantic-release] [@semantic-release/gitlab] › ℹ Uploaded file: /uploads/24c08e17680d23f5b07aef90ff1d33ee/VERSION.txt
[8:53:39 PM] [semantic-release] [@semantic-release/gitlab] › ℹ Uploaded file: /uploads/2456b13085aefd6b871c71a3f76d52b2/CHANGELOG.md
2021-07-26T12:53:39.355Z
semantic-release:gitlab Update git tag '1.1.2-develop.36' with commit '611ca8bf3e311bed3d97121a9622d22379c01a56' and release description
[8:53:39 PM] [semantic-release] › ✖ Failed step "publish" of plugin "@semantic-release/gitlab"
[8:53:39 PM] [semantic-release] › ✖ An error occurred while running semantic-release: { HTTPError: Response code 404 (Not Found)
at EventEmitter.emitter.on (/usr/local/share/.config/yarn/global/node_modules/got/dist/source/as-promise.js:118:31)
at process._tickCallback (internal/process/next_tick.js:68:7) name: 'HTTPError', pluginName: '@semantic-release/gitlab' }
{ HTTPError: Response code 404 (Not Found)
at EventEmitter.emitter.on (/usr/local/share/.config/yarn/global/node_modules/got/dist/source/as-promise.js:118:31)
at process._tickCallback (internal/process/next_tick.js:68:7) name: 'HTTPError', pluginName: '@semantic-release/gitlab' }
The text was updated successfully, but these errors were encountered: