New scripts to facilitate releases and merging upstream branches#60
Closed
jason-famedly wants to merge 3 commits into
Closed
New scripts to facilitate releases and merging upstream branches#60jason-famedly wants to merge 3 commits into
jason-famedly wants to merge 3 commits into
Conversation
jason-famedly
force-pushed
the
jason/release-updates-v2
branch
4 times, most recently
from
July 21, 2025 13:08
fcfdf0c to
5623246
Compare
jason-famedly
force-pushed
the
jason/release-updates-v2
branch
2 times, most recently
from
July 28, 2025 16:12
d2359ff to
05297ee
Compare
jason-famedly
force-pushed
the
jason/release-updates-v2
branch
from
August 7, 2025 16:18
05297ee to
7fccc80
Compare
Member
Author
|
Closing as it was decided to just remove the scripts in general |
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
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.
A rework of the original
make_release.shscript and a newmerge_upstream.shscript, separating these interests.Switch to a merge instead of a rebase of changes between Famedly and upstream repository's.
Release branches for Famedly going forward will be formatted as
famedly-release/vX.Yinstead of reusing therelease-vX.Yformat which matches upstream. This was fine before when rebasing was the go-to action. Now it is confusing and doesn't work cleanly.The new
merge_upstream.shscript should now be able to handle several common scenarios in a smart way. From the comments in the file itself:It is to be invoked with a single argument, the major and minor version of Synapse that is to be merged in. Use the format
vX.Yfor the argument. For example:Using various tags between our repo and upstreams it will determine that we have no release branch of our own(either locally on repo or remotely on Github), merge in the upstream branch for that version. If there was no changes to the upstream branch since the last time it was merged in, then it will just have the changes from our main branch.
Afterwards, it will (optionally) handle editing the CHANGES.md file for you, by selectively checking for Famedly exclusive changes which will be added to the bottom of the most recent Synapse version change(but above any pertaining 'release candidate' versions).
It will then recommend the tag to use for the release.
The
make_release.shscript still expects an argument in the formatvX.Y.Z_Afor use in tagging the release