Skip to content
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

[Help] Gitlab release generic package is labeled undefined #823

Open
CJP-Whitt opened this issue Feb 14, 2025 · 0 comments
Open

[Help] Gitlab release generic package is labeled undefined #823

CJP-Whitt opened this issue Feb 14, 2025 · 0 comments

Comments

@CJP-Whitt
Copy link

I am trying to create a release, and upload an asset to the release that gets saved as a generic package on gitlab. I see in the readme that if the asset path is a glob that only finds one file it should use that file name as the generic package name. But this is not the case. This results in generic package that is my correct file, but it is named "undefined" with no file extension.

I have already verified with an exec plugin that there is in fact only a single .pdf file in my project, and it seems that the fact that the asset labeled undefined being the file contents I desired proves that case.

FYI - I am using ../*.pdf for my path since my semrel config is stored within another directory.

Here is what my config looks like if you are curious:

plugins:
  # analyses the Git commits
  - - '@semantic-release/commit-analyzer'
    - preset: conventionalcommits
  # generates the release note from the Git commit messages
  - - '@semantic-release/release-notes-generator'
    - preset: conventionalcommits
  # generates the CHANGELOG.md file
  - - '@semantic-release/changelog'
    - changelogTitle: "# Changelog"
  # GitLab support
  - - '@semantic-release/gitlab'
    - assets: # save built pdf as generic package
      - path: "../*.pdf"
        target: "generic_package"

branches:
  - master
tagFormat: '${version}'

This seems to be a bug or incorrect functionality in documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant