JesseandClaude Sonnet 5
921db34b55
Submodule pinned to v0.7.7 (af68aac). current.ts bumped in place at 0.7.7:0 — no new version file, no migration: the change is to how the built client is cached, not to what it does. Every packaged build until now published ?v=nogit as its cache key (the .s9pk Dockerfile copies the tree in without .git, so git rev-parse fails), and serveStatic sent no Cache-Control at all — so 0.7.5's solitaire setup screen and 0.7.6's fix to it were both installed here correctly and neither ever reached a browser. Verified on phoenix.local against what the server actually returns, not just what was packed: build tag is 0.7.7-mtf7hyxc (not nogit) and the module graph's inner imports carry the same tag; play.html is no-cache; a ?v=-tagged module is immutable for a year; an untagged one is no-cache. Migration 0.7.6:0 -> 0.7.7:0 ran empty and both games in progress (WHISTLE-4086, COAL-7370) resumed with their same intent counts. README.md records that a hard reload is NOT a sufficient check for this class of bug — confirmed in the field on 0.7.6, where only a fresh private window showed the new build. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AdG46Ja2PEDBkpqiDazMoX
69 lines
5.5 KiB
TypeScript
69 lines
5.5 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.7:0',
|
|
releaseNotes: {
|
|
en_US:
|
|
'Bundles Station Master v0.7.7 \u2014 updates now actually reach your browser. Every packaged ' +
|
|
'release until now published its files under the same cache key, and the server never told ' +
|
|
'browsers when to look again, so a returning player kept running whichever version their ' +
|
|
'browser had already stored: the v0.7.5 solitaire setup screen and the v0.7.6 fix to it were ' +
|
|
'both installed correctly and neither was ever seen. Each build now carries its own key and ' +
|
|
"the pages are marked to revalidate, so this is the last update you'll have to open a private " +
|
|
'window to see. No rules changed; games in progress are unaffected.',
|
|
es_ES:
|
|
'Incluye Station Master v0.7.7: las actualizaciones ahora llegan de verdad a tu navegador. Hasta ' +
|
|
'ahora, cada versi\u00f3n empaquetada publicaba sus archivos bajo la misma clave de cach\u00e9, y el ' +
|
|
'servidor nunca indicaba a los navegadores cu\u00e1ndo volver a mirar, as\u00ed que quien regresaba segu\u00eda ' +
|
|
'ejecutando la versi\u00f3n que su navegador ya ten\u00eda guardada: la pantalla de configuraci\u00f3n del ' +
|
|
'solitario de la v0.7.5 y su correcci\u00f3n en la v0.7.6 se instalaron correctamente y nunca se ' +
|
|
'vieron. Ahora cada compilaci\u00f3n lleva su propia clave y las p\u00e1ginas se marcan para revalidarse, ' +
|
|
'as\u00ed que esta es la \u00faltima actualizaci\u00f3n que tendr\u00e1s que abrir en una ventana privada para ver. ' +
|
|
'Las reglas no han cambiado; las partidas en curso no se ven afectadas.',
|
|
de_DE:
|
|
'Enth\u00e4lt Station Master v0.7.7 \u2014 Aktualisierungen erreichen jetzt tats\u00e4chlich deinen Browser. ' +
|
|
'Bisher ver\u00f6ffentlichte jede paketierte Version ihre Dateien unter demselben Cache-Schl\u00fcssel, ' +
|
|
'und der Server teilte Browsern nie mit, wann sie erneut nachsehen sollten. Wer zur\u00fcckkam, ' +
|
|
'f\u00fchrte also weiter die Version aus, die sein Browser bereits gespeichert hatte: der ' +
|
|
'Solo-Einrichtungsbildschirm aus v0.7.5 und dessen Korrektur in v0.7.6 wurden beide korrekt ' +
|
|
'installiert und nie gesehen. Jeder Build tr\u00e4gt nun seinen eigenen Schl\u00fcssel, und die Seiten ' +
|
|
'sind zur erneuten Pr\u00fcfung markiert \u2014 dies ist also die letzte Aktualisierung, f\u00fcr die du ein ' +
|
|
'privates Fenster \u00f6ffnen musst. Keine Regel\u00e4nderungen; laufende Spiele sind nicht betroffen.',
|
|
pl_PL:
|
|
'Zawiera Station Master v0.7.7 \u2014 aktualizacje naprawd\u0119 docieraj\u0105 teraz do twojej przegl\u0105darki. ' +
|
|
'Do tej pory ka\u017cde wydanie publikowa\u0142o swoje pliki pod tym samym kluczem pami\u0119ci podr\u0119cznej, a ' +
|
|
'serwer nigdy nie m\u00f3wi\u0142 przegl\u0105darkom, kiedy sprawdzi\u0107 ponownie, wi\u0119c powracaj\u0105cy gracz nadal ' +
|
|
'uruchamia\u0142 t\u0119 wersj\u0119, kt\u00f3r\u0105 jego przegl\u0105darka ju\u017c zapisa\u0142a: ekran ustawie\u0144 gry solo z v0.7.5 i ' +
|
|
'jego poprawka z v0.7.6 zosta\u0142y poprawnie zainstalowane i nigdy nie zosta\u0142y zobaczone. Ka\u017cda ' +
|
|
'kompilacja ma teraz w\u0142asny klucz, a strony s\u0105 oznaczone do ponownej weryfikacji \u2014 to wi\u0119c ' +
|
|
'ostatnia aktualizacja, kt\u00f3r\u0105 trzeba otworzy\u0107 w oknie prywatnym, \u017ceby j\u0105 zobaczy\u0107. Zasady si\u0119 ' +
|
|
'nie zmieni\u0142y; gry w toku nie s\u0105 dotkni\u0119te.',
|
|
fr_FR:
|
|
'Inclut Station Master v0.7.7 \u2014 les mises \u00e0 jour atteignent enfin r\u00e9ellement votre navigateur. ' +
|
|
"Jusqu'ici, chaque version empaquet\u00e9e publiait ses fichiers sous la m\u00eame cl\u00e9 de cache, et le " +
|
|
'serveur ne disait jamais aux navigateurs quand regarder \u00e0 nouveau : un joueur qui revenait ' +
|
|
"continuait donc d'ex\u00e9cuter la version que son navigateur avait d\u00e9j\u00e0 stock\u00e9e. L'\u00e9cran de " +
|
|
'configuration du solo de la v0.7.5 et son correctif en v0.7.6 ont tous deux \u00e9t\u00e9 install\u00e9s ' +
|
|
'correctement et ne furent jamais vus. Chaque build porte d\u00e9sormais sa propre cl\u00e9 et les pages ' +
|
|
'sont marqu\u00e9es \u00e0 revalider : voici donc la derni\u00e8re mise \u00e0 jour que vous devrez ouvrir dans une ' +
|
|
"fen\u00eatre priv\u00e9e pour la voir. Aucune r\u00e8gle n'a chang\u00e9 ; les parties en cours ne sont pas " +
|
|
'affect\u00e9es.',
|
|
},
|
|
migrations: {
|
|
/**
|
|
* STILL NOTHING TO CARRY. v0.7.7 fixes how the built client is CACHED, not what it does: every
|
|
* packaged build published the same cache key (`?v=nogit` — the `.s9pk` build has no `.git` for
|
|
* `git rev-parse`) and the server sent no `Cache-Control` at all, so two correct releases never
|
|
* reached the browsers that asked for them. A build tag that varies and a revalidate header are
|
|
* both static-file concerns: no rule the engine enforces, no save-format change. A game in
|
|
* progress, on the server or in a browser, resumes exactly as it would have on v0.7.6.
|
|
*/
|
|
up: async ({ effects }) => {},
|
|
down: IMPOSSIBLE,
|
|
},
|
|
})
|