-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not create release if patterns matches multiple files with the same name. #265
Comments
This is the same issue as #158 Note:
In order to fix this, I've patched it such that the label of the file in the release isn't just the basename, but the relative path to the |
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#265, semantic-release#158
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#265, semantic-release#158
Hi ! Thanks for this lib :) I'am also experiencing the same issue as @EvanCarroll. I have a bunch of
Resulting in an error I've seen the PR from @EvanCarroll 267 that could manage to have unique label / name. Thanks |
The in-progress PR #267 is stale. Any help reviving it would be greatly appreciated! |
I'm getting this error,
This error comes right after a release
PUSH
. Currently it's silently failing failing I opened this ticket to fix the silent failing: #264You can see here that the problem is that GitLab errors with
400 (Bad Request)
because it's upload multiple files (in different directories) to the release API.I believe the solution for this should be to add the paths to the file's basename, relatively to the
pkgRoot
.The text was updated successfully, but these errors were encountered: