mirror of
https://github.com/screentinker/screentinker.git
synced 2026-08-13 13:53:12 -06:00
b29e3b4676
Cutting 1.9.31 turned a green tree red, and the failing assertion named a baseline rather than the tag that caused it. "Shipped source" was resolved as the newest v* tag. That is wrong at exactly one moment, and it is a moment that arrives at every release: on the release commit the newest tag IS HEAD, so shipped source becomes the working tree, every biconditional inverts, and the build demands BASELINE.web gain audio.volume — for displays that cannot have the fix until this very release reaches them. Tagging a release should not be able to change what the release is allowed to contain. A baseline describes an UN-UPDATED display, so the source it is judged against is the release BEFORE the one being cut. Skip any tag pointing at HEAD and use its predecessor: v1.9.30 here, and the newest tag as before during ordinary development. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014skWYXJUWhF73EvNPgB2AS |
||
|---|---|---|
| .. | ||
| config | ||
| db | ||
| lib | ||
| middleware | ||
| player | ||
| routes | ||
| scripts | ||
| services | ||
| test | ||
| ws | ||
| .gitignore | ||
| config.js | ||
| package-lock.json | ||
| package.json | ||
| server.js | ||
| smoke-ui.js | ||
| version.js | ||