Play your own Switch games on iPhone/iPad — one-click macOS app, no terminal. | 把 Switch 游戏装进 iPhone:图形界面一键构建,不用命令行。Bring your own game.
Swift apple-siliconcustom-formathomebrewiosipaipadipadosiphonemetalnative-portnintendo-switchnxnativeromfsswitch-games
RELEASING: bump the engine pin before -rc1, keep it between candidates
v0lumehicb79f4415024
diff --git a/RELEASING.md b/RELEASING.mdindex 6293d462..021a7e04 100644--- a/RELEASING.md+++ b/RELEASING.md@@ -6,8 +6,9 @@ A release starts as a release candidate. Players get the exact files of the cand### Cutting a candidate-1. The version bump goes to `main` first: `static let appVersion` in `frontend/Sources/NSPortBuilder/ContentView.swift`, and the changelog.-2. Tag a commit on `main` as `vX.Y.Z-rcN`, with N from 1: `git tag v0.7.6-rc1 <commit> && git push origin v0.7.6-rc1`.+1. Before `-rc1`, bump the engine pin, so the candidate carries the current engine. The nightly sync job opens the pull request `sync/upstream-<sha>` when seedds/nxnative has news. If it has not, `python3 tools/engine.py bump --dry --to main` shows which patches would conflict, and `python3 tools/engine.py bump --to <sha>` moves the pin. Merge that pull request before the version bump.+2. The version bump goes to `main` next: `static let appVersion` in `frontend/Sources/NSPortBuilder/ContentView.swift`, and the changelog.+3. Tag a commit on `main` as `vX.Y.Z-rcN`, with N from 1: `git tag v0.7.6-rc1 <commit> && git push origin v0.7.6-rc1`.`build-mac-app.yml` checks that the tag without `-rcN` is `appVersion`. The app inside says `0.7.6`, not `0.7.6-rc1`. The final release ships this bundle, and the app's own update installs only a bundle whose version is the release's.@@ -25,6 +26,8 @@ The candidate never touches the pre-release `engine-experimental`, which servesA candidate is built once. A second run of the same tag fails once the app is uploaded, because a rebuild would not be the same bytes. A broken build or a fix is the next candidate, `rc2`.+The pin stays between candidates. The final release ships the engine of its candidate, and its build stops when the engine zip differs. Bump the pin for `rc2` or later only for an engine fix that the release needs, and test that candidate as a whole again. A patch added to `patches/` also changes the `engine_id`, so a candidate with a new patch is tested as a whole too. Any other bump goes to `main` after the final tag, before the first candidate of the next version.+### Testing a candidateThe candidate's signed `latest.json` names the `engine_id` the release carries. The whole-app test checks that the app's first start, with its online engine check, lands on exactly that engine tree. The engine that `engine-experimental` serves that day does not count.