feat(home): Other versions on a build's row: go back to an older version of its channel, built in its place #119

Merged
HumanBean merged 1 commit from madebyjordan/LongshotLauncher:feat/older-versions into main 2026-11-15 22:59:04 +00:00
Member

Since #104 an update builds over its build in the same folder, so it replaces the version before it, and when a nightly breaks something there is no way back short of building that version again by hand. This adds Other versions to each build's row: pick an older version of the build's channel and the launcher builds it in the build's place, the same way an update does. Update then offers the newest again.

What changed

  • The row (HomeView.axaml): a clock button beside Open folder, shown when the build's channel has other versions on the server. It opens Other versions of … (VersionPickerView, VersionPickerViewModel).
  • The picker lists the channel's releases the server still has, newest first, each marked Older or Newer. It starts on the newest older one. It says the version is built in place of the current one, in its folder; that saves stay (every build shares them); and, on the nightly channel, that only the newest 5 nightlies are kept (docs/releases.md).
  • Building it is an update (JobKind.Update) to the picked tag, so nothing new runs: FolderOf, Replace, the shader-cache rule and the game-file links all work as for an update. BuildJob.Older only changes the words for an older tag: step 1 "Going back from … to …", the start button "Go back to …" (no up arrow), the build page "Going back to Longshot …" and the Ready page "Went back from …".
  • Core: OtherVersions.Of gives a build's choices from the release list the update check already read (Releases.Listed), so the picker asks the server nothing more. It covers only the build's own channel (another channel's version is Build another version). A track that is no channel gives none, so a pr build from #59 would get no list instead of an exception. ReleaseManifest.OnChannel is a channel's releases in version order; Newest is now its first.
  • The row's layout: on main, Delete is cut off on a selected row that isn't the default (Play this version, Set as default, Saves, the folder and Delete need more than the row's width in the 960-wide window). The left side now wraps, so the buttons on the right always show whole.
  • README ("An update stays in its build's folder"): how to go back. Every new text is in every catalog, and so is "Update to {0}": the start button of every update, which translations.py never found inside the one-line switch, so it showed in English.
  • tools/screenshots: home-other-versions, home-other-versions-second, other-versions, settings-go-back.

With #59: a pr build's track is not a channel, so its row shows no clock; its newer push stays "Update to" (Versions.Newer does not order pr- tags).

Not changed: docs/releases.md ("going down is the player's choice") is shared with Longshot's repository and stays true, so it is left alone. No new setting, no new file in the launcher's home.

Screenshots

From tools/screenshots, on Windows (960x600), in the comment below:

  • home-other-versions: the default build's row, the clock beside Open folder.
  • home-other-versions-second: a row that isn't the default, its left buttons wrapped so Delete shows.
  • other-versions: the picker on a nightly build.
  • settings-go-back: step 2 going back.

Testing

Windows 11, .NET SDK 10.0.404, on main @ d79e1e4.

  • tests/launcher_core/OtherVersionsChecks.cs (new): each channel's releases in version order (not the server's), drafts and duplicate tags left out, Newest = the first of OnChannel on all three channels, a build's other versions with Older/Newer, a stable build not offered release candidates, a build with no channel of its own following its version's track, a dev build, no list yet, and a channel holding only the build's own version.
  • python -I tests/test_launcher_core.py: on Windows the run stops at ShellLinkChecks, the same on main @ b1fd055 (the shell's shortcut on the test's Unicode scratch path), and Windows-only atomic-writer failures follow it. So the new checks and UpdatePolicyChecks were also run right after ReleaseNotesChecks, locally, and passed. The full run is CI's, on Linux.
  • dotnet build App/LongshotLauncher.csproj: 0 errors. dotnet format --verify-no-changes on the changed files: nothing on the lines changed here.
  • scripts/translations.py: every catalog lacks the same 25 texts as on main.
  • Merges: test-merged with every open PR that merges with main: #59 and #46 merge cleanly (this PR's lines are placed away from #59's, and the new catalog entries sit after "Rebuild {0}", not at the end each PR appends to), and so does #121. #74, #55, #50, #49 and #42 already conflict with main.

Not tested: a real go-back build end to end (no build was run here: the PC's game was in use). It runs the update path with an older tag. Building an older version over a newer one in place relies on make_game.py building over a folder, as an update does.

🤖 Generated with Claude Code

Since #104 an update builds over its build in the same folder, so it replaces the version before it, and when a nightly breaks something there is no way back short of building that version again by hand. This adds **Other versions** to each build's row: pick an older version of the build's channel and the launcher builds it in the build's place, the same way an update does. Update then offers the newest again. ## What changed - **The row** (`HomeView.axaml`): a clock button beside Open folder, shown when the build's channel has other versions on the server. It opens **Other versions of …** (`VersionPickerView`, `VersionPickerViewModel`). - **The picker** lists the channel's releases the server still has, newest first, each marked *Older* or *Newer*. It starts on the newest older one. It says the version is built in place of the current one, in its folder; that saves stay (every build shares them); and, on the nightly channel, that only the newest 5 nightlies are kept (docs/releases.md). - **Building it** is an update (`JobKind.Update`) to the picked tag, so nothing new runs: `FolderOf`, `Replace`, the shader-cache rule and the game-file links all work as for an update. `BuildJob.Older` only changes the words for an older tag: step 1 "Going back from … to …", the start button "Go back to …" (no up arrow), the build page "Going back to Longshot …" and the Ready page "Went back from …". - **Core:** `OtherVersions.Of` gives a build's choices from the release list the update check already read (`Releases.Listed`), so the picker asks the server nothing more. It covers only the build's own channel (another channel's version is *Build another version*). A track that is no channel gives none, so a `pr` build from #59 would get no list instead of an exception. `ReleaseManifest.OnChannel` is a channel's releases in version order; `Newest` is now its first. - **The row's layout:** on main, Delete is cut off on a selected row that isn't the default (Play this version, Set as default, Saves, the folder and Delete need more than the row's width in the 960-wide window). The left side now wraps, so the buttons on the right always show whole. - **README** ("An update stays in its build's folder"): how to go back. Every new text is in every catalog, and so is "Update to {0}": the start button of every update, which `translations.py` never found inside the one-line switch, so it showed in English. - **tools/screenshots:** `home-other-versions`, `home-other-versions-second`, `other-versions`, `settings-go-back`. With #59: a `pr` build's track is not a channel, so its row shows no clock; its newer push stays "Update to" (`Versions.Newer` does not order `pr-` tags). Not changed: docs/releases.md ("going down is the player's choice") is shared with Longshot's repository and stays true, so it is left alone. No new setting, no new file in the launcher's home. ## Screenshots From `tools/screenshots`, on Windows (960x600), in the comment below: - `home-other-versions`: the default build's row, the clock beside Open folder. - `home-other-versions-second`: a row that isn't the default, its left buttons wrapped so Delete shows. - `other-versions`: the picker on a nightly build. - `settings-go-back`: step 2 going back. ## Testing Windows 11, .NET SDK 10.0.404, on main @ d79e1e4. - `tests/launcher_core/OtherVersionsChecks.cs` (new): each channel's releases in version order (not the server's), drafts and duplicate tags left out, `Newest` = the first of `OnChannel` on all three channels, a build's other versions with Older/Newer, a stable build not offered release candidates, a build with no channel of its own following its version's track, a `dev` build, no list yet, and a channel holding only the build's own version. - `python -I tests/test_launcher_core.py`: on Windows the run stops at `ShellLinkChecks`, the same on main @ b1fd055 (the shell's shortcut on the test's Unicode scratch path), and Windows-only atomic-writer failures follow it. So the new checks and `UpdatePolicyChecks` were also run right after `ReleaseNotesChecks`, locally, and passed. The full run is CI's, on Linux. - `dotnet build App/LongshotLauncher.csproj`: 0 errors. `dotnet format --verify-no-changes` on the changed files: nothing on the lines changed here. - `scripts/translations.py`: every catalog lacks the same 25 texts as on main. - Merges: test-merged with every open PR that merges with main: #59 and #46 merge cleanly (this PR's lines are placed away from #59's, and the new catalog entries sit after "Rebuild {0}", not at the end each PR appends to), and so does #121. #74, #55, #50, #49 and #42 already conflict with main. Not tested: a real go-back build end to end (no build was run here: the PC's game was in use). It runs the update path with an older tag. Building an older version over a newer one in place relies on make_game.py building over a folder, as an update does. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(home): Other versions on a build's row: go back to an older version of its channel, built in its place
Some checks failed
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Compile and test (pull_request) Has been cancelled
294b0209db
Since updates stay in their build's folder (#104), an update replaces the version before it, and the only way back was to
build that version again by hand. Other versions (the clock on a build's row) lists its channel's other releases the
server still has (every release and release candidate, the newest 5 nightlies) and builds the one picked as an update
does: in the build's folder, its row then that version, saves shared. An older one says "Go back to", and Update then
offers the newest again.

- Core/OtherVersions.cs and ReleaseManifest.OnChannel (Newest is now its first), checked in OtherVersionsChecks.cs
- BuildJob.Older: the wizard's words for going back (step 1, the start button, the build page, the Ready page)
- The row's actions: the left side wraps, so its buttons on the right always show whole (Delete was cut off on a
  row that is not the default)
- tools/screenshots: home-other-versions(-second), other-versions, settings-go-back

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Author
Member

Screenshots (tools/screenshots, Windows, 960x600): the default build's row with the clock beside Saves; a row that isn't the default, its left buttons wrapped so Delete shows; the picker on a nightly build; step 2 going back.

home-other-versions
home-other-versions-second
other-versions
settings-go-back

home-other-versions.png

home-other-versions-second.png

other-versions.png

settings-go-back.png

Screenshots (tools/screenshots, Windows, 960x600): the default build's row with the clock beside Saves; a row that isn't the default, its left buttons wrapped so Delete shows; the picker on a nightly build; step 2 going back. ![home-other-versions](home-other-versions.png) ![home-other-versions-second](home-other-versions-second.png) ![other-versions](other-versions.png) ![settings-go-back](settings-go-back.png) ![home-other-versions.png](https://git.magicbean.dev/attachments/736b61cf-ff12-43e5-8498-f0da9beff971) ![home-other-versions-second.png](https://git.magicbean.dev/attachments/ab417ecb-0065-4d6e-9b15-8954a80fc84a) ![other-versions.png](https://git.magicbean.dev/attachments/f2699a75-0699-445d-9f96-6f52606c3008) ![settings-go-back.png](https://git.magicbean.dev/attachments/5bd9be30-0b67-4bf4-ab8c-74f3e0257c49)
madebyjordan changed title from WIP: feat(home): Other versions on a build's row: go back to an older version of its channel, built in its place to feat(home): Other versions on a build's row: go back to an older version of its channel, built in its place 2026-11-15 22:10:23 +00:00
madebyjordan force-pushed feat/older-versions from 294b0209db
Some checks failed
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Compile and test (pull_request) Has been cancelled
to cece011e96
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Compile and test (pull_request) Blocked by required conditions
2026-11-15 22:25:27 +00:00
Compare
Author
Member

Pushed cece011 (force, rebased on main @ d79e1e4, nothing else changed in behaviour): the clock moved beside Open folder and this PR's lines moved away from #59's, so #59, #46 and #121 now merge cleanly with it; the new catalog entries sit after "Rebuild {0}" instead of at the end. Checks re-run as in the description; screenshots below are from cece011.

Pushed cece011 (force, rebased on main @ d79e1e4, nothing else changed in behaviour): the clock moved beside Open folder and this PR's lines moved away from #59's, so #59, #46 and #121 now merge cleanly with it; the new catalog entries sit after "Rebuild {0}" instead of at the end. Checks re-run as in the description; screenshots below are from cece011.
Author
Member

Screenshots at cece011 (tools/screenshots, Windows, 960x600):

home-other-versions
home-other-versions-second
other-versions
settings-go-back

home-other-versions.png

home-other-versions-second.png

other-versions.png

settings-go-back.png

Screenshots at cece011 (tools/screenshots, Windows, 960x600): ![home-other-versions](home-other-versions.png) ![home-other-versions-second](home-other-versions-second.png) ![other-versions](other-versions.png) ![settings-go-back](settings-go-back.png) ![home-other-versions.png](https://git.magicbean.dev/attachments/1f34f6ff-667a-4377-a61a-bb7604ef96ca) ![home-other-versions-second.png](https://git.magicbean.dev/attachments/1c378bfa-713c-4127-a5b3-1f6adba68182) ![other-versions.png](https://git.magicbean.dev/attachments/155b28a7-be50-465a-b8b3-4db02ab9a232) ![settings-go-back.png](https://git.magicbean.dev/attachments/55dd4450-1408-43da-b4aa-feb2ae7fe728)
HumanBean deleted branch feat/older-versions 2026-11-15 22:59:04 +00:00
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Compile and test (pull_request) Blocked by required conditions
Some workflows are waiting to be reviewed.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/LongshotLauncher!119
No description provided.