JesseandClaude Sonnet 5
3b7b334968
Submodule pinned to v0.7.8 (193800a). current.ts bumped in place at 0.7.8:0 — no new version file, no migration: the change is which screen a solitaire visit lands on, plus the splash footer's wording. Both are client-side, and a solitaire save lives in the browser rather than on this server, so nothing here is involved either way. 0.7.5 skipped the setup screen whenever the browser held a save, and any browser that has ever played solitaire holds one — so the door could never reach the screen again. The door outranks a save now; a bare reload still resumes; #ss-resume keeps the game in progress reachable since Deal clears it. Verified on phoenix.local against what the server returns: the door carries ?solitaire, play.html carries #ss-resume and #ss-saved-note, the footer names both ways to play, and the build tag is 0.7.8-mtfaojtv. Migration 0.7.7:0 -> 0.7.8:0 ran empty and both multiplayer games in progress (WHISTLE-4086, COAL-7370) resumed with their same intent counts. The behaviour itself is covered by four new tests upstream that reproduce the reported state (door + existing save) rather than by reading served output — which is what the two previous attempts did, and why they were reported as verified while still being wrong. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AdG46Ja2PEDBkpqiDazMoX
70 lines
5.4 KiB
TypeScript
70 lines
5.4 KiB
TypeScript
import { IMPOSSIBLE, VersionInfo } from '@start9labs/start-sdk'
|
|
|
|
export const current = VersionInfo.of({
|
|
// `<upstream>:<downstream>` — the upstream half tracks the bundled Station Master tag exactly
|
|
// (`versions.md`'s consistency checklist), so bumping the submodule pin and bumping this are one
|
|
// action. The downstream half moves only for packaging-only changes, and RESETS to `:0` when the
|
|
// upstream half moves.
|
|
version: '0.7.8:0',
|
|
releaseNotes: {
|
|
en_US:
|
|
'Bundles Station Master v0.7.8 \u2014 the solitaire setup screen finally works for everyone. It was ' +
|
|
'skipped whenever your browser held a saved solitaire game, and any browser that has ever ' +
|
|
'played holds one, so most players never saw it at all. Clicking Play solitaire now always ' +
|
|
'asks how you want the game set up. Your game in progress is safe: the screen offers Continue ' +
|
|
'saved game, and says plainly that dealing a new one replaces it. Simply reopening the page ' +
|
|
'still resumes where you left off, as before. The homepage footer now also names both ways to ' +
|
|
'play. No rules changed; games in progress are unaffected.',
|
|
es_ES:
|
|
'Incluye Station Master v0.7.8: la pantalla de configuraci\u00f3n del solitario por fin funciona para ' +
|
|
'todos. Se omit\u00eda siempre que el navegador ten\u00eda una partida de solitario guardada, y cualquier ' +
|
|
'navegador que haya jugado alguna vez tiene una, as\u00ed que la mayor\u00eda de los jugadores nunca la ' +
|
|
'vio. Al pulsar Jugar en solitario ahora siempre se te pregunta c\u00f3mo quieres configurar la ' +
|
|
'partida. Tu partida en curso est\u00e1 a salvo: la pantalla ofrece Continuar partida guardada e ' +
|
|
'indica claramente que repartir una nueva la reemplaza. Volver a abrir la p\u00e1gina sigue ' +
|
|
'retom\u00e1ndola donde la dejaste, como antes. El pie de la p\u00e1gina de inicio ahora tambi\u00e9n nombra ' +
|
|
'las dos formas de jugar. Las reglas no han cambiado; las partidas en curso no se ven afectadas.',
|
|
de_DE:
|
|
'Enth\u00e4lt Station Master v0.7.8 \u2014 der Solo-Einrichtungsbildschirm funktioniert endlich f\u00fcr alle. ' +
|
|
'Er wurde \u00fcbersprungen, sobald der Browser ein gespeichertes Solospiel hielt, und jeder Browser, ' +
|
|
'der je gespielt hat, h\u00e4lt eines \u2014 die meisten Spieler sahen ihn also nie. Ein Klick auf Solo ' +
|
|
'spielen fragt jetzt immer, wie das Spiel eingerichtet werden soll. Dein laufendes Spiel ist ' +
|
|
'sicher: der Bildschirm bietet Gespeichertes Spiel fortsetzen und sagt deutlich, dass ein neues ' +
|
|
'Austeilen es ersetzt. Die Seite einfach erneut zu \u00f6ffnen setzt wie bisher dort fort, wo du ' +
|
|
'aufgeh\u00f6rt hast. Die Fu\u00dfzeile der Startseite nennt jetzt au\u00dferdem beide Spielarten. Keine ' +
|
|
'Regel\u00e4nderungen; laufende Spiele sind nicht betroffen.',
|
|
pl_PL:
|
|
'Zawiera Station Master v0.7.8 \u2014 ekran ustawie\u0144 gry solo wreszcie dzia\u0142a dla wszystkich. By\u0142 ' +
|
|
'pomijany zawsze, gdy przegl\u0105darka przechowywa\u0142a zapisan\u0105 gr\u0119 solo, a ka\u017cda przegl\u0105darka, kt\u00f3ra ' +
|
|
'kiedykolwiek gra\u0142a, tak\u0105 przechowuje \u2014 wi\u0119c wi\u0119kszo\u015b\u0107 graczy nigdy go nie zobaczy\u0142a. ' +
|
|
'Klikni\u0119cie Zagraj solo zawsze pyta teraz, jak chcesz ustawi\u0107 gr\u0119. Twoja gra w toku jest ' +
|
|
'bezpieczna: ekran oferuje Kontynuuj zapisan\u0105 gr\u0119 i jasno m\u00f3wi, \u017ce rozdanie nowej j\u0105 zast\u0105pi. ' +
|
|
'Zwyk\u0142e ponowne otwarcie strony nadal wznawia gr\u0119 w miejscu, w kt\u00f3rym sko\u0144czy\u0142e\u015b. Stopka strony ' +
|
|
'g\u0142\u00f3wnej wymienia teraz r\u00f3wnie\u017c oba sposoby gry. Zasady si\u0119 nie zmieni\u0142y; gry w toku nie s\u0105 ' +
|
|
'dotkni\u0119te.',
|
|
fr_FR:
|
|
"Inclut Station Master v0.7.8 \u2014 l'\u00e9cran de configuration du solo fonctionne enfin pour tout le " +
|
|
'monde. Il \u00e9tait ignor\u00e9 d\u00e8s que le navigateur d\u00e9tenait une partie solo sauvegard\u00e9e, et tout ' +
|
|
'navigateur ayant d\u00e9j\u00e0 jou\u00e9 en d\u00e9tient une : la plupart des joueurs ne l\u2019ont donc jamais vu. ' +
|
|
'Cliquer sur Jouer en solitaire demande d\u00e9sormais toujours comment configurer la partie. Votre ' +
|
|
'partie en cours est en s\u00e9curit\u00e9 : l\u2019\u00e9cran propose Continuer la partie sauvegard\u00e9e et indique ' +
|
|
'clairement qu\u2019en distribuer une nouvelle la remplace. Rouvrir simplement la page reprend ' +
|
|
'toujours o\u00f9 vous en \u00e9tiez. Le pied de page de l\u2019accueil nomme maintenant les deux fa\u00e7ons de ' +
|
|
"jouer. Aucune r\u00e8gle n'a chang\u00e9 ; les parties en cours ne sont pas affect\u00e9es.",
|
|
},
|
|
migrations: {
|
|
/**
|
|
* STILL NOTHING TO CARRY. v0.7.8 changes which SCREEN a solitaire visit lands on — the setup
|
|
* screen was skipped whenever the browser held a save, so a returning player never saw it — plus
|
|
* the splash footer's wording. Both are client-side; no rule the engine enforces and no
|
|
* save-format change.
|
|
*
|
|
* A SOLITAIRE SAVE LIVES IN THE BROWSER, not on this server, so nothing here can touch it either
|
|
* way: `#ss-resume` is what keeps it reachable, and only the player's own Deal clears it. A
|
|
* multiplayer game in progress resumes exactly as it would have on v0.7.7.
|
|
*/
|
|
up: async ({ effects }) => {},
|
|
down: IMPOSSIBLE,
|
|
},
|
|
})
|