feat(home): Other versions on a build's row: go back to an older version of its channel, built in its place #119
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!119
Loading…
Reference in a new issue
No description provided.
Delete branch "madebyjordan/LongshotLauncher:feat/older-versions"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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).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.Olderonly 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 …".OtherVersions.Ofgives 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 aprbuild from #59 would get no list instead of an exception.ReleaseManifest.OnChannelis a channel's releases in version order;Newestis now its first.translations.pynever found inside the one-line switch, so it showed in English.home-other-versions,home-other-versions-second,other-versions,settings-go-back.With #59: a
prbuild's track is not a channel, so its row shows no clock; its newer push stays "Update to" (Versions.Newerdoes not orderpr-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 ofOnChannelon 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, adevbuild, 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 atShellLinkChecks, 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 andUpdatePolicyCheckswere also run right afterReleaseNotesChecks, locally, and passed. The full run is CI's, on Linux.dotnet build App/LongshotLauncher.csproj: 0 errors.dotnet format --verify-no-changeson the changed files: nothing on the lines changed here.scripts/translations.py: every catalog lacks the same 25 texts as on 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
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.
WIP: feat(home): Other versions on a build's row: go back to an older version of its channel, built in its placeto feat(home): Other versions on a build's row: go back to an older version of its channel, built in its place294b0209dbcece011e96Pushed
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 fromcece011.Screenshots at
cece011(tools/screenshots, Windows, 960x600):