hyper-expanse / semantic-delivery-gitlab Goto Github PK

Hi, I'm trying to use this on Gitlab CI both using docker and npm but for docker I'm getting error

semantic-delivery-gitlab failed for the following reason - Error: No valid "repository" data found in package metadata. Please see https://docs.npmjs.com/files/package.json#repository for proper syntax.

Just a heads up:

Hi,

When running the following command:
semantic-delivery-gitlab --token xxxxxxxxx

I've got the following error:
semantic-delivery-gitlab failed for the following reason - Error: Failed to create GitLab release through API: Response code 403 (Forbidden)

My token have API right.

Thank you for your help.

Using url

• registry.gitlab.com/hyper-expanse/open-source/semantic-delivery-gitlab:9.0.0
  the pipeline it's broken (error it's access denied)

We also tried to open urls

• https://gitlab.com/hyper-expanse/open-source/semantic-delivery-gitlab/container_registry
• registry.gitlab.com/hyper-expanse/open-source/semantic-delivery-gitlab:9.0.0
  the error is 404

Dependency vulnerability: yargs-parser
Patched in: >=13.1.2 <14.0.0 || >=15.0.1 <16.0.0 || >=18.1.2

@hutson/semantic-delivery-gitlab > conventional-commits-detector > meow > yargs-parser
@hutson/semantic-delivery-gitlab > conventional-gitlab-releaser > meow > yargs-parser
@hutson/semantic-delivery-gitlab > get-pkg-repo > meow > yargs-parser
@hutson/semantic-delivery-gitlab > git-semver-tags > meow > yargs-parser

First of all thanks for the good work on this package. The above vulnerability is currently a blocker for our CI/CD pipelines. It would be great if we can put a fix for this. Thanks!

My existing repo has v2.1.0 tags,

$ git tag -l
1.2.0
v1.3.0
v1.3.1
v1.3.2
v1.3.3
v1.3.5
v2.0.0
v2.0.1
v2.0.2
v2.0.3
v2.0.4
v2.0.5
v2.1.0
v2.1.0-rc.0
v2.1.0-rc.1
v2.1.0-rc.2

but semantic-delivery-gitlab wants to create 2.1.1 for a patch

$ DEBUG=semantic-delivery-gitlab npx semantic-delivery-gitlab --dry-run -t $GITLAB_TOKEN
  semantic-delivery-gitlab latest tag v2.1.0 +0ms
  semantic-delivery-gitlab commit messages - [ 'chore(ci): add pipeline\n\n' ] +9ms
  semantic-delivery-gitlab detected angular commit convention +2ms
  semantic-delivery-gitlab using angular commit convention +0ms
  semantic-delivery-gitlab recommended version bump is - {
  semantic-delivery-gitlab   level: 2,
  semantic-delivery-gitlab   reason: 'There are 0 BREAKING CHANGES and 0 features',
  semantic-delivery-gitlab   releaseType: 'patch'
  semantic-delivery-gitlab } +22ms
  semantic-delivery-gitlab version to be released 2.1.1 +1ms
  semantic-delivery-gitlab posting release to 'https://gitlab.example.net/api/v4/' using preset 'angular' +0ms
  semantic-delivery-gitlab posting to the following issues - [] +0ms
Deleted tag '2.1.1' (was c68a122)
No release created during dry run.

Title is self explanatory, any chance we can get a feature/option to auto update the package.json version, to match what the cli detects the next version to be? do this commit then release that commit as the tagged copy?

So we increment then tag?