The last feature release, and the first in maintenance mode: DLSS 5
Neural Rendering, x6 / Dynamic / Custom frame generation, a Custom LUT,
Qodana next to SonarCloud, the maintenance-mode policy and this week's
dependency fold.
CHANGELOG entry; ROADMAP release section and closing line; SECURITY
supported versions 1.6.x; version references in ARCHITECTURE, TECH-SPEC
(and its test count), PACKAGING, FEATURES, CONTENT-INVENTORY (+ vi),
DISCLAIMER (+ vi) and the bug / accessibility forms; the six manifests
1.5.2 -> 1.6.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
YTDescGen is feature-complete; from 1.6.0 on it is maintained, not
extended. Still accepted: scheduled dependency updates; fixes for high or
critical CVEs and serious runtime issues; major language / runtime /
framework upgrades; bug, UI/UX and accessibility fixes, and options added
to or removed from the app's lists when people really need them;
translation fixes; Cloudflare / Worker changes the platform forces and
website incidents.
- README: status, CI, Qodana and SonarCloud badges; a Project status
section; Contributing and the Roadmap row follow it.
- CONTRIBUTING: a Maintenance mode section, Option requests, issue and
pull request rules, What We Want / Don't Want.
- SECURITY, MAINTAINERS, CLAUDE.md: the policy where each one needs it.
- ROADMAP: status block, a Maintenance mode section, Phase 5 and the
backlog frozen. FEATURES: the extension points are frozen.
- Issue forms: Feature request removed; Option request and Translation or
wording fix added; Bug report and Accessibility barrier now carry the
`needs-triage` label (`triage` never existed). config.yml points feature
ideas at Discussions → Ideas. The PR template gains a Scope checklist.
- maintenance-triage.yml closes, with a bilingual comment and the
`out-of-scope` label, feature issues and `feat:` pull requests from
outside contributors (scopes options, a11y and i18n stay open) and
anything labelled `out-of-scope`. pull_request_target without checkout;
listed under zizmor's dangerous-triggers ignore with the reason.
Labels created on the repository: out-of-scope, needs-triage, i18n,
option-request.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Video settings:
- NVIDIA frame generation gains x6 (the multiplier was already in the list
but offered by no vendor) and Dynamic Multi Frame Generation (DLSS 4.5).
- "Custom…" for every vendor reveals a text field (`frameGenCustom`); the
description prints what was typed, like a custom graphics preset, and
nothing for an empty box.
- A "DLSS 5 Neural Rendering" switch (`dlssNeuralRendering`), shown for
NVIDIA only and printed after the DLSS mode:
"Ultra - NVIDIA DLSS Quality + NVIDIA DLSS 5 Neural Rendering + NVIDIA
Dynamic Multi Frame Generation". Another vendor turns it off
(`coerceDlssNeuralRendering`: the vendor switch, applied profiles and
templates, backup import).
- Editor store v21 -> v22 back-fills both fields.
- composeGraphicsPart's vendor half moves into small helpers.
My Rig: "Custom" is the LUT field's first suggestion (typing it works too,
any case). The rig block then prints just "LUT applied" in the output
language ("Có áp dụng LUT") instead of "LUT: Custom" — a field's
`customNoteKey`. No migration: the rig is a string map.
i18n: the new editor and description keys in all 8 locales and
_schema.json; brand names stay English. tests/engine/graphics-vendor.test.ts
also holds every vendor's options to their labels in the schema.
Docs: FEATURES (upscaler / frame-gen table, LUT Custom), TECH-SPEC (input
fields, store v22, rig block), CLAUDE.md (how to add an option).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Maintenance (#245, #248): Tauri 2.12.5 with the fixes its window,
webview and single-instance layers collected since 2.12.4, and this
week's dependency updates; i18next stays on 26.6.x to keep the initial
load inside its budget.
- CHANGELOG v1.5.2, ROADMAP entry and status
- docs: TECH-SPEC's package.json listing follows the real file again
and notes the i18next hold
- version references: ARCHITECTURE, TECH-SPEC, PACKAGING, FEATURES,
DISCLAIMER + Vietnamese, the bug-report and accessibility templates
- six manifests 1.5.1 -> 1.5.2
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Accessibility (#238, #239): AA contrast, generated text marked with its
language, page names read out after a navigation, the single-key
shortcut switch, desktop zoom hotkeys, and ACCESSIBILITY.md in the repo,
the Legal Center and on the website.
- CHANGELOG v1.5.1, ROADMAP entry and status
- docs: ARCHITECTURE (RouteAnnouncer, settings, capabilities), TECH-SPEC
(singleKeyShortcuts, contrast test, test count), PACKAGING (zoom
hotkeys and permission), FEATURES
- version references: DISCLAIMER + Vietnamese, the bug-report template
- six manifests 1.5.0 -> 1.5.1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- ACCESSIBILITY.md (+ docs/i18n/vi): goal (WCAG 2.2 AA, not a conformance
claim), what works with a keyboard, screen readers, zoom, motion and touch,
how it is checked, supported environments, known limitations, how to
report a barrier (severity, response), and a checklist for contributors.
- In the Legal Center (consent: false, English + Vietnamese) and as
/legal/accessibility on the website; the Turnstile page's footer links it
in all eight languages.
- .github: Accessibility barrier issue form (label `accessibility`), an
Accessibility option in the feature request scope, an accessibility
checklist in the PR template.
- README, CONTRIBUTING, DEVELOPMENT (+vi), FEATURES and CLAUDE.md point to
it; SECURITY.md's supported versions move from 1.3.x to 1.5.x.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upscaled video (#235): "Upscaled from" in Video settings, the
[4K Upscaled] title badge, the Upscale line in VIDEO SETTINGS and an
automatic tech note about upscaled detail.
- CHANGELOG v1.5.0, ROADMAP entry and status
- docs: FEATURES, CONTENT-INVENTORY (+ Vietnamese), ARCHITECTURE and
TECH-SPEC (upscale.ts, store v21, test count), CLAUDE.md
- version references: PACKAGING, DISCLAIMER + Vietnamese, the
bug-report template
- six manifests 1.4.0 -> 1.5.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A LUT field in My Rig (#230), the boss's name as a tag in boss videos
(#231), and this week's dependency updates (#228, #229).
- CHANGELOG v1.4.0, ROADMAP entry and status
- version references: ARCHITECTURE, TECH-SPEC (+ test count), PACKAGING,
FEATURES, DISCLAIMER + Vietnamese, the bug-report template
- six manifests 1.3.2 -> 1.4.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Boss Fight and Boss No Hit videos get the boss's name as a tag of its
own, right after the game's name, so fitting the list to 500 characters
never drops it.
bossNameTag cleans the Boss Name field the way a search term reads:
- NFC first; everything but letters (any script), marks, digits,
whitespace and in-word ' ' - becomes a space: , : ; ! ? quotes,
brackets, &, the CJK brackets and dots, (TM), emoji.
- A dot stays between digits ("Phase 2.0"), goes between initials
("S.T.A.L.K.E.R." -> "STALKER") and is a space anywhere else
("Mr.X" -> "Mr X"). Done per word in code: a lookbehind would be a
syntax error in the macOS 11-13 webview and stop the chunk loading.
- Over 30 characters, the name before its title ("Loretta, Knight of
the Haligtree" -> "Loretta"), else the leading words that fit; the
word fit is now a helper shared with tagFriendlyGameName (same result
there).
Only the video types whose extraFields include bossName add it, so a
boss name left in the draft after switching to Full Gameplay is not
tagged. Docs: FEATURES, ARCHITECTURE 2.3, TECH-SPEC.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new My Rig field for the LUT graded in the video editor. The
description and the social captions print it on its own line right
under the editor ("LUT: Arri Alexa LogC to Rec709"); left empty, there
is no line.
- Typing offers the LUTs that come with DaVinci Resolve, named the way
its LUT menu shows them (from Resolve 21's own LUT folder); any other
name is printed as typed.
- cleanLutName tidies a pasted file name or path: Explorer's "Copy as
path" or a macOS path keeps only the file name, and a .cube / .dat /
.3dl / .csp / .ilut / .olut / .look extension goes. Dots inside a
name ("SLog3SGamut3.CineToLC-709") stay.
- RigField gets `clean` (CPU and LUT) and `wide`. The cleaner runs when
the field loses focus and again in formatRigValue, so Ctrl/Cmd+Shift+C
or Ctrl/Cmd+S pressed with the cursor still in the field prints the
tidy name too; the LUT field spans both columns, under the editor row.
- `rig.lut` and `description.rigLabels.lut` ("LUT") in all eight
locales and _schema.json; a test now holds both label sets to
RIG_FIELDS.
No store migration: the rig is a flat string map in the channel
profile.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rate limiting for the website: Workers Rate Limiting bindings in front
of the gate, behind a WAF rate limiting rule at the zone (#220).
- CHANGELOG v1.3.2, ROADMAP entry and status
- version references: ARCHITECTURE, TECH-SPEC (+ test count), PACKAGING,
FEATURES, DISCLAIMER + Vietnamese, the bug-report template
- six manifests 1.3.1 -> 1.3.2
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tauri 2.12.4, the desktop's Save / Open dialogs off the async workers
(#216), SonarCloud in CI (#215) and this week's dependency updates with
alert #49 closed (#217).
- CHANGELOG v1.3.1, ROADMAP entry and status
- version references: ARCHITECTURE, TECH-SPEC, PACKAGING, FEATURES,
DISCLAIMER + Vietnamese, the bug-report template
- six manifests 1.3.0 -> 1.3.1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Docs had drifted since 1.0.0: README missed the 1.1.0 features and
showed an Android step that overwrites the committed Gradle project;
ROADMAP, PACKAGING, ARCHITECTURE and TECH-SPEC still described 1.0.0;
CONTRIBUTING and the PR template listed half the gates; SECURITY named
1.0.x; CLAUDE.md's structure and gate list were out of date.
webapp/TAURI.md (Node 25, no .rpm) is folded into PACKAGING and removed.
Also: purpose-word validation documented in ARCHITECTURE, two stale code
comments (about.ts, vietnamese-banks.ts), .gitignore for the
maintainer's local note files, and the CHANGELOG entry.
Six manifests bumped 1.1.0 -> 1.2.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new content-warning group, AI-generated content (7): general, art /
visuals, voices, music / sound, text / dialogue, generated live while
playing, and disclosed by the developer. It follows Steam's AI
disclosure (made with AI during development vs generated live while the
game runs); machine translation stays the Language patch field.
Also simulated gambling and in-game purchases (ESRB / PEGI descriptors
with no warning so far), and a tech note for upscaling / frame-generation
artifacts (which upscaler was on is already the Video settings line).
A test now fails when a content warning or tech note has no editor label
or description bullet in _schema.json, and so in any locale; tech notes
get the group-parity test content warnings already had.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- CHANGELOG: v1.1.0 (copyright email and purpose words, Hide scrollbars,
installer copyright string, copyright-year check, the rust-toolchain pin)
- FEATURES: the four split contact lines, purpose words, the Settings row,
the profile's emails
- TECH-SPEC / ARCHITECTURE: editor store v20, hideScrollbars without a
settings bump, theme-init and App applying the scrollbar class, the new
CI step and scripts
- DEVELOPMENT (en + vi), CLAUDE.md: check:copyright / update:copyright
- I18N: 1,253 UI + 574 template keys per locale
- six manifests 1.0.0 -> 1.1.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every claim checked against the code.
- TECH-SPEC: current configs (React 19 / Vite 8 / Tailwind 4, the web vs
Tauri build), Cloudflare hosting and the Worker, store versions and
migrations, the backup format, engine rules added in 1.0, CI as it is.
- ARCHITECTURE: layers, web vs Tauri, routing and start-up, the engine,
state, backup & restore, web delivery, the hardened Tauri shell.
- PACKAGING: tauri.conf and capabilities as shipped, the eleven
name-only commands and what they guard, where desktop data lives, the
first-start recovery of pre-1.0 files, the release workflows; the
auto-update flow that never existed is gone.
- FEATURES, CONTENT-INVENTORY (+ vi): recounted from config (42 genres,
16 store entries, 22 social/donate fields, 7 cross-post platforms,
37 Vietnamese banks); shortcuts that never existed removed.
- DEVELOPMENT (+ vi): main-only branching, every npm script, Rust 1.90,
Cloudflare local dev with test keys, the Rust checks.
- I18N: both namespaces and all seven registration places, including
the check page's own language list; ROADMAP: v1.0.0 shipped + backlog.
- DISCLAIMER (vi): eight languages. The locale template script now
prints the full registration checklist; a stale comment in main.tsx
about the removed settings file is corrected.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two new locales, 1,562 strings each, complete: titles, every description
block, all 248 content warnings, tech notes, playthrough notes, pinned
comments, playlist copy, and the whole interface.
Brazil is a top-three market for gameplay viewing and Indonesia the largest in
Southeast Asia. Both use Latin script, so neither needed font or layout work.
**docs/I18N.md was wrong about what registering a locale takes**, and this
release is where that bit. It claimed `SUPPORTED_LANGUAGES` was "the only
registration step". It is one of four, and they fail differently:
SupportedLanguage union compile error
CORE_TAGS_BY_LANG compile error (there are TWO such records,
MULTILINGUAL_TAGS compile error not one — the doc mentioned one)
detectBrowserLanguage SILENT
The silent one matters most: the language works perfectly and simply never
auto-selects for a visitor whose browser is set to it. `SUPPORTED_LANGUAGES`
also wasn't type-bound to the union, and every consumer casts, so a mismatch
between the first two compiled cleanly — it now carries a `satisfies` clause.
`tests/i18n/locale-registration.test.ts` exists to close those gaps: it checks
the picker list against the locale directories on disk in BOTH directions, plus
namespace files, flags, native names and tag pools.
Browser-language detection now matches the full BCP-47 tag before the bare
language, or `pt-BR` would be reduced to `pt` and never found. Any other
Portuguese variant resolves to pt-BR rather than falling through to English.
115 UI keys were not hand-translated at all: their English text is
byte-identical to a string already translated in templates.json (graphics
presets, ray-tracing modes, difficulty names, content-warning labels), so they
are copied across. Translating those twice risks a checkbox and the rendered
description disagreeing about what the same option is called.
Deliberately left in English, matching what the Spanish locale already does:
vendor product names (NVIDIA DLSS, AMD FSR, Intel XeSS, Fluid Motion Frames),
platform brands, hardware acronyms, genre terms that are loanwords in both
languages, and example URLs/emails in placeholders. So pt-BR reads 1,344/1,562
and id 1,308/1,562 "differing from English" — the remainder are those
pass-throughs, not gaps.
Both are AI-translated and NOT native-reviewed. Recorded in DISCLAIMER.md
alongside JA/ES/KO/ZH.
Also replaces `__dirname` in the Vite and Vitest configs with
`import.meta.dirname` — Vite 8's native config loader doesn't provide the CJS
global and warned on every run.
v0.36.0 is skipped: the dependency release shipped first and took 0.37.0.
Tests 692 → 698. Validator now 1,562 keys x 8 locales.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
**docs/I18N.md was wrong in a way that would waste a contributor's afternoon.**
It said adding a locale to `SUPPORTED_LANGUAGES` was "the only registration
step". It is one of four, and the missing ones fail differently: the
`SupportedLanguage` union is a compile error, `MULTILINGUAL_TAGS` is a compile
error, but `detectBrowserLanguage`'s own hardcoded copy of the list fails
*silently* — the language works and simply never auto-selects for a visitor
whose browser is set to it. Also noted: `SUPPORTED_LANGUAGES` is not type-bound
to the union and every consumer casts, so a mismatch compiles cleanly.
Also documents the `--copy-english` / `--force` flags on the locale generator,
which only started existing in v0.35.0 despite having been advertised in
package.json since v0.1.
Elsewhere:
- **DEVELOPMENT.md** — the five new npm scripts, including why `format:check`
excludes markdown and locale JSON, and why `typecheck:all` exists.
- **TECH-SPEC.md** — the real CI job, a new Field Limits section, and how
over-limit enforcement derives from the engine's long-ignored `warnings`.
- **ARCHITECTURE.md** — the settings→engine mapping and its two guards, the
two-source validation state, and an honest note that the first Strict Mode
implementation typechecked, passed tests, and did nothing.
- **FEATURES.md** — the settings table still listed `Default Genre` and
`Auto-save Draft`, removed in v0.22.0 and v0.3. Replaced, plus a guardrails
section.
- **README.md** — guardrails in the feature list, and a link to the wiki.
The wiki itself (12 pages: quick start, glossary, field reference, guardrails,
batch/social, import-export, languages, privacy, troubleshooting, FAQ, release
process) is published separately — it lives in its own repository.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add an explicit "Requirements & tested versions" section for the Android build:
- Minimum Android 11 (minSdk 30), target Android 16 (targetSdk 36), universal ABIs.
- Tested Android 11 -> 16 on emulators, plus a real device on Android 12.
- Rationale for the Android 11 floor: device coverage, a modern auto-updating
WebView (why the Android 12 real device worked but a stale WebView-91 emulator
black-screened), and component-level security upkeep (Play system updates /
Play services / WebView) since OS bulletins for 11-13 have ended.
Touches docs/PACKAGING.md, docs/FEATURES.md, README.md only — no code change.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Build and package the app for Android from the same Tauri 2 codebase, shipping
an installable, sideloadable signed APK alongside the desktop binaries.
Build / packaging
- cfg-gate desktop-only tray / single-instance / hide-to-tray / exit-prevention
in lib.rs behind #[cfg(desktop)]; move tauri-plugin-single-instance to a
desktop-only target table so the library compiles for Android.
- `cargo tauri android init` -> committed gen/android Gradle project; release
signingConfigs read keystore.properties (gitignored, from CI secrets locally).
- .github/workflows/release-android.yml: JDK 17 + Android SDK/NDK + rust targets,
decode keystore from secrets, build --apk, upload to the same draft release.
- vite.config.ts: es2020 build.target for Tauri builds (older-WebView safety).
Runtime fixes (found via on-device testing)
- External links: a real tap on `<a target="_blank">` makes the Android WebView
fire onCreateWindow, which Tauri tries to satisfy via the shell plugin's open
(no such binary on Android -> uncaught error, nothing opens). Strip
target="_blank" from external anchors and route clicks through the opener
plugin in the capture phase. (open-external.ts, main.tsx)
- Boot black screen on old WebViews: crypto.randomUUID() (Chrome/WebView 92+)
ran at module load and threw on WebView 91. Fall back to a manual RFC 4122 v4
built on getRandomValues. (uuid.ts; +4 regression tests, 509 -> 513)
- File export on Android routes through the in-WebView blob download. (IS_MOBILE)
Compatibility
- minSdk 30 (Android 11+), targetSdk 36 (Android 16): covers the large majority
of active devices with a modern, patched WebView + Google Play system updates.
Release: bump manifests 0.28.0 -> 0.29.0; docs (README, FEATURES, PACKAGING,
CHANGELOG). Verified on an Android 13 emulator (render, links, export).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Two new warning groups — Dialogue / Language (10) and Internet / Digital
life (18) — plus 5 color phobias, 5 suggestive-imagery disclosures, 2
body-image phenomena, and an educational/PSA-purpose disclosure: 207 -> 248
ids across 12 groups. 504 new locale strings (84 keys x 6 locales), VI
flag-prone labels masked per the v0.21.0 precedent. Backfills the
content-inventory docs (audio group + v0.23.0 VFX items were never
documented) and replaces the stale v0.7 warning lines in FEATURES.md.
Adds 8 tests incl. a CONTENT_WARNINGS <-> groups parity guard. Five
manifests bumped 0.24.2 -> 0.25.0.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Security/deps: react-router 6.30.3→6.30.4 (moderate open-redirect patch, non-breaking) and vitest 3.2.4→4.1.8 (clears the dev-only critical Vitest-UI advisory); all 482 tests pass unchanged on the new major. npm audit now reports 0 vulnerabilities. Removed unused serde/serde_json from src-tauri/Cargo.toml (no refs in src-tauri/src/; cargo check confirms the crate still compiles). Documented the cross-post caption generator (Social tab) in README + docs/FEATURES.md. Five manifests bumped 0.24.0→0.24.1.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Bundles five changes for the v0.19.0 release:
- Content warnings: +28 IDs (25 clinical phobias in the phobias group,
3 discrimination terms in the sensitive group); 97 -> 125 total,
fully translated across all 6 locales. Purely additive.
- Dead-code sweep: add knip tooling (knip.json + npm run knip); remove
the unused use-debounce.ts hook and ~13 unreferenced exports; tighten
~12 symbols to module-private.
- Security: npm audit fix for the brace-expansion moderate DoS
(transitive dev dependency, 5.0.5 -> 5.0.6).
- UI: scroll-to-top floating button that scrolls the AppShell <main>.
- Docs: accuracy pass across TECH-SPEC, ROADMAP, FEATURES,
CONTENT-INVENTORY (+ vi mirror), CHANGELOG, README.
Version bumped 0.18.0 -> 0.19.0 across all five manifests.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>