You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like requested in the issue #838 I open a new bug.
Like I said, we practice the trunk base development and we release from trunk.
We use Python Semantic Release with Gitlab and we have a specific configuration file with a little more commit type.
We have a first job to make pre-release versions and a second to make final release versions.
Until PSR 9.5.0 we have no problem, but since 9.6.0 the incrementation of pre-release version is not incremented on the last release version:
I have a pre-release version 0.2.0-beta.3 and I make an 0.2.0 release version on the same branch.
I release a patch and PSR make me a 0.2.0-beta.4. And when I make the release I have a 0.2.1 release version.
In resume: 0.2.0-beta.3 -> 0.2.0 -> 0.2.0-beta.4 -> 0.2.1
Expected behavior
I have a pre-release version 0.2.0-beta.3 and I make an 0.2.0 release version on the same branch.
I release a new pre-release patch 0.2.1-beta.1 and after a couple of beta version I make a release 0.2.1.
I would like: 0.2.0-beta.3 -> 0.2.0 -> 0.2.1-beta.1 -> 0.2.1
Environment
We use a docker image based on python:3.12-alpine and versions are:
Until PSR 9.6.0 everything works perfectly. We are actually blocked on version 9.5.0.
Copy of your message:
Initially looking at your git history, it looks like PSR is behaving as expected if the commits are parsed with the AngularParser (ie. Conventional Commit standard). build and chore do not trigger a version bump unless otherwise configured. By default only a fix and perf commit type trigger a patch bump.
Separately, I'm not sure what you meant by the statement: releases are based on tag and not on a specific branch. PSR selects the prerelease token & prerelease value and whether or not it should release based on which branch it is on. Common usage of trunk based developers use the default branch to release or use ReleaseFlow branching to have separate branches to perform releases. Ultimately though, PSR will not automatically be able to determine if it should be a prerelease or a regular release if you are releasing these from the same branch. Manual intervention via command line arguments can make this possible.
Thanks for your time.
Best Regards.
The text was updated successfully, but these errors were encountered:
@JeromeCheviet, I think I know the answer now based on what changed from 9.5 to 9.6. I probably should have made it a breaking change just in case but you live and learn. I am very sorry it messed up your workflow.
If you could try swapping --prerelease with --as-prerelease and it should return to your expected result.
The problem
Hello,
Like requested in the issue #838 I open a new bug.
Like I said, we practice the trunk base development and we release from trunk.
We use Python Semantic Release with Gitlab and we have a specific configuration file with a little more commit type.
We have a first job to make pre-release versions and a second to make final release versions.
Until PSR 9.5.0 we have no problem, but since 9.6.0 the incrementation of pre-release version is not incremented on the last release version:
I have a pre-release version 0.2.0-beta.3 and I make an 0.2.0 release version on the same branch.
I release a patch and PSR make me a 0.2.0-beta.4. And when I make the release I have a 0.2.1 release version.
In resume: 0.2.0-beta.3 -> 0.2.0 -> 0.2.0-beta.4 -> 0.2.1
Expected behavior
I have a pre-release version 0.2.0-beta.3 and I make an 0.2.0 release version on the same branch.
I release a new pre-release patch 0.2.1-beta.1 and after a couple of beta version I make a release 0.2.1.
I would like: 0.2.0-beta.3 -> 0.2.0 -> 0.2.1-beta.1 -> 0.2.1
Environment
We use a docker image based on python:3.12-alpine and versions are:
We use poetry for our projects.
Configuration
PSR configuration:
Build-system configuration:
Logs
logs for the command:
semantic-release -vv version --prerelease --no-push
:psr_logs.txt
Additional context
Until PSR 9.6.0 everything works perfectly. We are actually blocked on version 9.5.0.
Copy of your message:
Thanks for your time.
Best Regards.
The text was updated successfully, but these errors were encountered: