Update release process to use release branches#486
Merged
Conversation
ebrahimebrahim
force-pushed
the
update-release-process
branch
from
July 20, 2026 15:42
ab10a46 to
b810266
Compare
ebrahimebrahim
enabled auto-merge (rebase)
July 20, 2026 15:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
At first I wanted to keep the release process simpler for openlifu-python, but I think that was a mistake on my part.
This updates the release process with one small but important change: we should use release branches. Otherwise the process is the same. Now this brings openlifu-python into parity with the extension and desktop app, which both use release branches.
The amount of textual changes is because I also simplified the document text. Process-wise all that's changing is: use release branches!
The reason for the change is: Sometimes when we need to patch the extension of the desktop application the fix needs to take place in openlifu-python. To do that properly we need to use the same same release line of openlifu-python with just a patch fix on top. To do that, we need release branches, and we must never increment the patch version of openlifu-python directly on the main line.
Related: