-
Notifications
You must be signed in to change notification settings - Fork 1
Creating new branches
-
Bump
branch
,runtime-branch
to new SDK branch; change extensions andappend-path
if necessary. https://github.com/flathub/org.flatpak.Builder.BaseApp/blob/f4138223f55ae4117cf47a71ea1b6152ee029a03/org.flatpak.Builder.BaseApp.json#L3-L13 -
Add new extension to https://github.com/flathub/org.flatpak.Builder.BaseApp/blob/f4138223f55ae4117cf47a71ea1b6152ee029a03/.github/workflows/ci.yml#L35
-
Create a test branch for https://github.com/flathub/org.flatpak.Builder and update the wheels in
flatpak-builder-lint-deps.json
to the Python version in new SDK No need to update anything else. -
Change https://github.com/flathub/org.flatpak.Builder.BaseApp/blob/f4138223f55ae4117cf47a71ea1b6152ee029a03/.github/workflows/ci.yml#L52 to that test branch
-
Commit
org.flatpak.Builder.BaseApp.json, .github/ci.yml
and any other modified files, make a PR and start a test build. -
If test build and smoketest are successful, create a new branch,
branch/2x.08
and merge PR to it. (For maintainers) -
Once the
2x.08
update for org.flatpak.Builder is merged, switch the test branch to master again in https://github.com/flathub/org.flatpak.Builder.BaseApp/blob/f4138223f55ae4117cf47a71ea1b6152ee029a03/.github/workflows/ci.yml#L52