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

Adding releaseAs=preminor && preid=beta doesn't work as expected #792

Open
ak274 opened this issue Mar 15, 2024 · 1 comment
Open

Adding releaseAs=preminor && preid=beta doesn't work as expected #792

ak274 opened this issue Mar 15, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@ak274
Copy link

ak274 commented Mar 15, 2024

If a package is at v0.3.0-beta.0 and I run target to increment a version with the following config

{
        "preset": "angular",
        "push": true,
        "commitMessageFormat": "chore({projectName}): release version ${version} [skip ci]",
        "baseBranch": "HEAD:develop",
        "noVerify": true,
        "releaseAs": "preminor",
        "preid": "beta"
      }

It should update the version v0.3.0-beta.1 but it actually calculated version v0.4.0-beta.0 which is wrong.

@ak274 ak274 changed the title Adding releaseAs=preminor && preid=beta doesn't work as expected Adding releaseAs=preminor && preid=beta doesn't work as expected Mar 15, 2024
@ak274
Copy link
Author

ak274 commented Apr 29, 2024

@edbzn This is long pending request and blocking us to update package its occurred in latest version. Please help.

@edbzn edbzn added the bug Something isn't working label Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants