question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Prerelease not incrementing

See original GitHub issue

Hello, I have the following configuration in my workflow and when pushing to my prerelease branch, the patch number is incrementing rather than the prerelease number.

- name: Bump Application Version and Tag
  id: tag_version
  uses: mathieudutour/github-tag-action@v5.5
  with:
    github_token: ${{ secrets.GITHUB_TOKEN }}
    release_branches: master
    pre_release_branches: releases/*
    append_to_pre_release_tag: prerelease

Example: The previous tag was v1.0.3-prerelease.0. I pushed a new commit to the branch and the new tag was v1.0.4-prerelease.0, not v1.0.3-prerelease.1. Do I need to change the default_bump? Is there a setting for incrementing the prerelease number when nothing is specified? Thanks

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:9 (6 by maintainers)

github_iconTop GitHub Comments

2reactions
JonEricksoncommented, Oct 16, 2021

Hi @dploeger, this is what I have for my prerelease workflow. I have not run it against version 5.6.

  - name: Bump Application Version and Tag
    id: tag_version
    uses: mathieudutour/github-tag-action@v5.5
    with:
      github_token: ${{ secrets.GITHUB_TOKEN }}
      default_bump: release
      release_branches: master
      pre_release_branches: releases/*
      append_to_pre_release_tag: prerelease
2reactions
JonEricksoncommented, Aug 19, 2021

I will get a PR going to address this soon if the author does not address it sooner.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Pre-release versioning not incrementing correctly ... - GitHub
I was attempting to create a pre-release format that allows me to limit the increments of our beta pre-release to only be bumped...
Read more >
Semantic-Release - pre-release version not incrementing for ...
1. However, another feat commit doesnt increment the version to v1.1.0-next.1. It just creates v1.0.0-next.2.
Read more >
Version Incrementing - GitVersion
Semantic Versioning is all about releases, not commits or builds. ... (which will increment the SemVer every commit) all builds must have a...
Read more >
Semantic Versioning 2.0.0 | Semantic Versioning
Patch and minor versions MUST be reset to 0 when major version is incremented. A pre-release version MAY be denoted by appending a...
Read more >
Bump - Commitizen
It is possible to specify a prerelease (alpha, beta, release candidate) version. ... -d DEVRELEASE specify non-negative integer for dev. release --increment ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found