How would I make a hotfix/patch release to an older branch/release
See original GitHub issueHi,
Is it possible to be able to release from a fixes/hotfix/stable whatever branch?
E.g. master is ahead at 4.3.1. But I’m looking to release a security patch to 2.0.1 from a release2.0
branch for it to become 2.0.2.
How would I go about that in standard-version? Or is that scenario not supported?
Fritz
P.S. I’ve been looking through the issues, and the most similar ones to mine are those about named versions (#83, #84). But that’s not what I mean.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Git Flow: best approach for a hotfix for an older version being ...
Either put the hotfix patch into the v1.1.0 release or - if that is to late - create a new hotfix for v1.1.1....
Read more >Gitflow release branch process from start to finish example
The Gitflow release branch is made from the develop branch and gets merged into both master and develop when finished.
Read more >How to release a hotfix step by step - Operations
Set up the maintenance branch you want to merge your fixes into. # Define your new 'maintenance' branch export base=v27. · Update package.json...
Read more >Git-flow: How to create a hotfix release when there are future ...
Since your release branches are now long-lived, you can create your hotfix branch off the release branch instead of the tag.
Read more >Hotfix — git-flow 1.0 documentation - Read the Docs
In that case, you will have to: rename your hotfix branch,; update the code. Assuming the 1.3.3 version has been released from another...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Tapppi I don’t suppose you could be enlisted to add your notes to the README, I never feel like I fully followed what might be an appropriate workflow for hotfixes either.
Sorry if this is already answered (I had a hard time following the
git-semver-tags
stuff), but is there an easy way of merging the changelog entries from the older release branch back into themaster
changelog?For context, I added a patch to an older release and now I want that release to be documented in the
master
changelog. It’s in the changelog in therelease/x
branch but not inmaster
.