See Release Che-Theia workflow.
To make another bugfix release of Che-Theia with the upstream Theia patch included, there're several options available.
- switch to the required Che-Theia tag, e.g. 7.27.x
- update the
build.include
file to match upstream Eclipse Theia revision:THEIA_COMMIT_SHA="<commit-sha>"
- continue the release process as usual
- clone the Theia fork https://github.com/redhat-developer/eclipse-theia
- sync the
master
branch of the forked repository with the origin one and push the changes - take the Theia commit sha which was used for a Che-Theia release, e.g. for 7.27.x it's
1110f990
- create a new branch
- cherry-pick the required commit sha to the created branch and push the changes
- update the
build.include
file:THEIA_GITHUB_REPO="redhat-developer/eclipse-theia"
THEIA_BRANCH="<created-branch-name>"
THEIA_COMMIT_SHA="<commit-sha>"
- push the changes
- continue the release process as usual
It's also possible to use a diff file to patch the Theia while releasing Che-Theia:
- prepare a
*.patch
file - put it into the
patches
folder and a sub-folder which name corresponds to theTHEIA_VERSION
value, e.g.master
- continue the release process as usual