Skip to content

prefix not working properly? #31

@jbakholt

Description

@jbakholt

I have a repository tagged with x/v1.0.0

Now when configuring semver-action like this:

  - name: Get Next Version
    id: semver
    uses: ietf-tools/semver-action@v1.5.1
    with:
      token: ${{ github.token }}
      branch: main
      noVersionBumpBehavior: current
      prefix: x/

I get this:

Run ietf-tools/semver-action@v1.5.1
with:
token: ***
branch: main
noVersionBumpBehavior: current
prefix: x/
minorList: feat, feature
patchList: fix, bugfix, perf, refactor, test, tests
patchAll: false
skipInvalidTags: false
Comparing against latest tag: x/v1.0.0
/home/runner/work/_actions/ietf-tools/semver-action/v1.5.1/dist/index.js:4998
const error = new requestError.RequestError(toErrorMessage(data), status, {
^

RequestError [HttpError]: Not Found
at /home/runner/work/_actions/ietf-tools/semver-action/v1.5.1/dist/index.js:4998:21
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async main (/home/runner/work/_actions/ietf-tools/semver-action/v1.5.1/dist/index.js:31171:24) {
status: 404,

What am I doing wrong? If I omit the prefix i get "Latest tag is invalid (does not conform to semver)!"

So clearly the prefix does something...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions