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
Unclear how to release a patch of an old version #861
Comments
This is definitely supposed to be a supported ability via release branches but I do believe there likely is a bug with tag resolution that I haven't been able to solve yet. |
This is the correct location for general support questions as of now.
I have simulated your scenario as much as I understood and PSR will provide The configuration concept I used is documented under the Mulitbranch releases section of the documentation. In your case, you are creating a second non-prerelease channel for the special release branch that will diverge from the original history.
This image below was the truncated git history that I generated to test your scenario. When I execute the following command with the semantic-release version --print
# 0.2.12 If this does not work in your scenario, please provide some detail on your merging/branching strategy or a log of your git history in graph format ( |
Ok, I didn't try without prerelease so this is likely the issue.
Thanks, this looks similar to https://semantic-release.gitbook.io/semantic-release/recipes/release-workflow/maintenance-releases |
This is not the correct documentation. The link above is for the JavaScript variant of semantic-release which is similar but not this project's docs. Correct Link: Multibranch Releases |
refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology. This removes the reliance on any last full release that is not within the history of the current branch. Resolves: python-semantic-release#861
refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology. This removes the reliance on any last full release that is not within the history of the current branch. Resolves: python-semantic-release#861
Yes I realize that, apologies, I was referencing that doc as an example of what I was trying to accomplish-- the multibranch release doc is similar, but the nodejs version matched our exact use case more closely. |
refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology. This removes the reliance on any last full release that is not within the history of the current branch. Resolves: python-semantic-release#861
refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology. This removes the reliance on any last full release that is not within the history of the current branch. Resolves: python-semantic-release#861
refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology. This removes the reliance on any last full release that is not within the history of the current branch. Resolves: python-semantic-release#861
refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology. This removes the reliance on any last full release that is not within the history of the current branch. Resolves: python-semantic-release#861
refactor duplicate logging messages and flow to process out odd cases in a fail fast methodology. This removes the reliance on any last full release that is not within the history of the current branch. Resolves: python-semantic-release#861
I wasn't able to find a forum for general questions, so if there's a better place to ask general support questions... please let me know.
That said, I am trying to understand how we would configure
python-semantic-release
to enable us to release a patch version or hotfix of an old version. In our code base we have versions like0.2.11
and0.15.12
-- if we currently have0.2.11
pushed to a production environment and need to release a patch (or hotfix) version (for example0.2.12
or0.2.12-hotfix.1
if attempting a "prerelease") when usingpython-semantic-version
it seems to want the next release to be0.15.13
.In this scenario we've created a branch from an old version of our
main
branch where the last tagged version is0.2.11
-- so the "next" release we'd expect is0.2.12
or0.2.12-hotfix.1
.Is there a pattern or path where we could implement our expected behavior? Thanks!
The text was updated successfully, but these errors were encountered: