docs(changelog): one queue per console (#335 step 1)

Hardware (Phat, FW 5.10, web UI via Playwright):
1. Jak X base (3.6 GB) stream install running; its patch and a third
   package queued behind it as Queued (#1)/(#2) — no refusal. Base then
   patch installed; the game launched patched. PASS
2. Star Wars base + patch stream installs in sequence; launched. PASS
3. The third package's file was renamed before its turn: only that row
   failed, with the reason and Retry; the others finished. PASS
4. Page reload mid-queue: not exercised on hardware (covered by the
   browser-build unit test).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
phantomptrandClaude Opus 5.5 committed 2026-09-27 21:58:53 -07:00
1 parent c40b0951b4
commit ff18bd2b2b
1 file changed
+19
+19
View File
@@ -4,6 +4,25 @@ What's new in ps5upload, written for humans.
---
## Unreleased
**One queue for each console.**
- **Queue stream installs.** Stream installs, links, library installs and
External Packages now all go into the console's queue and run one after
another — no more "Another install is in progress", and a running install
no longer greys out the buttons for the next one. A game's update and DLC
always install after the game itself, whatever order you queue them in.
- **See the queue where you install.** Install Package shows the console's
queue at the top: what is installing, and each waiting item's place in
line. The console tab shows how many items are waiting.
- **Retry via upload.** If the PS5 can't reach this computer for a stream
install, its queue row offers to upload the package and install it instead.
- An install that was running when the app closed is never re-run by itself —
check the game, then retry if needed. Queued links aren't saved to disk.
---
## 5.36.0
**Choose which drive install packages are kept on.**