GitHub Automation
Overview
Repository automation lives under .github/**. The release path is centered on .github/…/update.yml, a manually dispatched workflow that takes wsa_ver, wsa_message, and release_type (WIF or retail). Its first check job checks out the repo, installs Python scraping dependencies, creates or switches to an update branch, clones LSPosed/MagiskOnWSALocal twice, downloads update-check scripts from this repository's master branch, and runs the Magisk Stable, Magisk Canary, KernelSU, and MindTheGapps checks. Those scripts communicate release-note values through environment variables such as MAGISK_STABLE_MSG, KERNEL_SU_MSG, and MTG_MSG; .github/…/update.yml then commits changed *.appversion files to the update branch with stefanzweifel/git-auto-commit-action and deletes prior Check update workflow runs.
After check, .github/…/update.yml runs check-and-create-tag. That job derives three release tags from wsa_ver: Windows_11_<version>, Windows_11_<version>_arm64, and Windows_10_<version>. It checks for existing tags with mukunku/tag-exists-action, downloads release-note templates from maintainer gists based on release_type, fills placeholders such as <<DATEOFRELEASE>>, <<MTGPACKAGENAME>>, and <<KERNELSUVERSION>>, then creates the empty GitHub releases with softprops/action-gh-release. WIF releases are named WSABuilds LTS ...; retail releases are named Windows Subsystem For Android ....
The same .github/…/update.yml then fans out to reusable build workflows. For WIF, it schedules x64 and arm64 matrices covering no-root, Magisk, Magisk Canary, KernelSU, GApps/no-GApps, and Amazon Appstore removal combinations. Most WIF no-root/Magisk jobs call .github/…/build.yml for x64 or .github/…/buildarm64.yml for arm64, while KernelSU jobs use .github/…/build_old.yml and .github/…/build_arm64_old.yml. For retail, all listed build jobs use the old workflows. Each fan-out job passes the same wsa_ver, gappsver, amazonflag, root, magiskver, devicemodel, and compression inputs into the called workflow and inherits repository secrets.
.github/…/build.yml is the active x64 reusable build. It is only triggered by workflow_call. On Ubuntu it checks out the repo, sets up Python with a pip cache for MagiskOnWSA/scripts/, creates a virtualenv from MagiskOnWSA/…/requirements.txt, installs apt packages including xmlstarlet, then runs MagiskOnWSA/…/build.sh with the supplied architecture/root/GApps/Amazon options and --release-type WIF. After build output is available, it runs MagiskOnWSA/…/houdini_installer.sh, compresses the Windows 11 output as <artifact>.7z, patches the generated AppxManifest.xml in MagiskOnWSA/output/<artifact_folder> for Windows 10 compatibility, downloads patched DLLs from MustardChef/WSAPatch, compresses a second <artifact>_Windows_10.7z, and uploads both archives to the pre-created GitHub releases tagged Windows_11_<wsa_ver> and Windows_10_<wsa_ver>.
.github/…/buildarm64.yml is the active arm64 reusable build. It follows the same Ubuntu setup against MagiskOnWSA/scripts/, calls MagiskOnWSA/…/build.sh, compresses the output to <artifact>.7z, derives the Windows_11_<wsa_ver>_arm64 tag, and uploads the archive to that release. Unlike the active x64 workflow, it does not perform the Windows 10 manifest/DLL patch or produce a Windows 10 artifact.
.github/…/build_old.yml and .github/…/build_arm64_old.yml are the legacy reusable builders. They use MagiskOnWSAOld/scripts/ and MagiskOnWSAOld/…/build.sh, then pass the raw output to a second make-pri job on windows-latest with actions/upload-artifact/actions/download-artifact. The Windows job runs MakePri.ps1 for x64 resource merging or copies the Windows SDK arm64 makepri.exe, compacts system, product, system_ext, and vendor VHDX images with diskpart, compresses the output, and uploads it to the release. The x64 old workflow additionally patches and publishes a Windows 10 archive; the arm64 old workflow publishes only the Windows 11 arm64 archive. The active builders have their Windows post-processing largely commented out and instead compress/upload from Ubuntu, so review changes to active and old workflows separately.
.github/…/buildtester.yml is the manual testing workflow. It exposes workflow_dispatch choices for target Windows version, architecture, release channel, optional insider user_code, root solution, GApps brand, device model, compression, and Amazon removal. It rejects the unsupported Windows 10 + arm64 combination, maps user-facing choices to MagiskOnWSA/…/build.sh arguments, writes the insider code into MagiskOnWSA/download/.ms_account, builds with --after-compress, then transfers MagiskOnWSA/output to a Windows job using actions/cache/save and actions/cache/restore. The Windows job merges PRI resources, compacts VHDX files, optionally applies the Windows 10 patch, compresses/checksums .7z outputs, and uploads GitHub Actions artifacts rather than publishing releases.
Dependency and repository-maintenance automation is smaller. .github/dependabot.yml asks Dependabot to check GitHub Actions updates daily at the repository root, so action version bumps affect all workflow files above. .github/FUNDING.yml exposes Ko-fi funding for mustardchef. Issue intake is configured by .github/…/config.yml, which disables blank issues and points users to the README FAQ and Discord support, plus .github/…/bug_report.yml, .github/…/feature_request.yml, and .github/…/documentation.yml, which apply bug, enhancement, and documentation labels and collect the release/build context reviewers need.
Coupling
- If MagiskOnWSA/…/build.sh or MagiskOnWSAOld/…/build.sh changes its GitHub Actions outputs, update .github/…/build.yml, .github/…/buildarm64.yml, .github/…/build_old.yml, .github/…/build_arm64_old.yml, and .github/…/buildtester.yml; they read
steps.wsa.outputs.artifact,artifact_folder, andbuiltto locate output folders, name archives, transfer artifacts, and tag release uploads. - If release tag naming changes in .github/…/update.yml, update every reusable build workflow's release-tag preparation at the same time. .github/…/update.yml creates
Windows_11_<version>,Windows_11_<version>_arm64, andWindows_10_<version>releases before the build jobs upload files to those exact tags. - If adding a new root/GApps/device/build variant in .github/…/update.yml, choose the active versus old reusable workflow deliberately. WIF no-root/Magisk variants generally use .github/…/build.yml or .github/…/buildarm64.yml, while retail and KernelSU variants are wired to .github/…/build_old.yml or .github/…/build_arm64_old.yml.
- If the Windows 10 patch changes, update both active and old x64 paths. .github/…/build.yml, .github/…/build_old.yml, and .github/…/buildtester.yml each remove manifest capabilities, lower
TargetDeviceFamilyMinVersion, and download the same three DLLs fromMustardChef/WSAPatch; drift means test artifacts and release artifacts can behave differently. - If
MakePri.ps1or the output folder layout changes, verify .github/…/build_old.yml, .github/…/build_arm64_old.yml, and .github/…/buildtester.yml. Their Windows jobs callMakePri.ps1or write intooutput/<artifact>/output/<artifact_folder>paths and then compact named VHDX partitions. - If action versions are bumped by .github/dependabot.yml, review workflow syntax in the files using those actions, not just Dependabot's diff. Several workflows use major-version action references such as
actions/checkout@v7,actions/upload-artifact@v7, and cache actions whose input/output behavior controls artifact handoff.
Risks
- .github/…/update.yml has inconsistent tag-check references: the Windows 11 x64 stop condition uses
steps.checkTag.outputs.exists, but the step id ischeckTag1; later debug lines also echosteps.checkTag.outputs.existsfor arm64 and Windows 10. If a tag already exists, the intended guard may not stop the workflow, and release creation or later asset upload can fail after some releases were already created. - .github/…/buildarm64.yml and .github/…/build_old.yml compute
RLS_TYPEfrominputs.release_type, butrelease_typeis not declared as aworkflow_callinput and the build commands hard-code--release-type WIFor--release-type latest. If callers expect the reusable workflow to honor retail/WIF through that variable, the generated WSA source channel can be wrong. - .github/…/buildtester.yml references
needs.build.outputs.artifact_folderin the Windows 10 patch, but thebuildjob only exportsartifact,built, anddate. A Windows 10 test run can patch the wrong path or fail when it tries to open AppxManifest.xml. - .github/…/build_arm64_old.yml defines
artifact_folder: ${{ steps.wsa.outputs.artifact_folder }}}with an extra}. Any downstream path using that output can resolve incorrectly, breaking Windows resource merging or upload for arm64 old builds. - .github/…/build.yml, .github/…/build_old.yml, and .github/…/buildtester.yml download Windows 10 patch DLLs from external
MustardChef/WSAPatchraw URLs during the run. If those URLs move or the files change unexpectedly, release artifacts can become unreproducible or fail late after the WSA build has completed.