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>
The first Qodana run found 74 problems in TypeScript / JavaScript and 12 in
Rust. Fixed:
- React 19.3 deprecates `FormEvent`: the three save forms take the
`SubmitEvent` their `onSubmit` hands them.
- The URL patterns read `\S` instead of `[^\s]` (18 patterns in platforms.ts
and playtest-platforms.ts, same characters).
- public/theme-init.js declares its browser globals and drops an unused
catch binding.
- The two private `stable()` JSON helpers (restore.ts, library-apply.ts)
become one `stableJson()` in src/utils/stable-json.ts, with a test.
- vitest.config.ts reuses vite.config.ts's alias map instead of a copy.
- Accordion destructures `icon` as `Icon` instead of copying it, a JSDoc
link points at nothing any more, and i18next's `init()` promise is
`void`ed on purpose.
- Rust: the three "show the main window" blocks become `show_main_window`.
Excluded in qodana.yaml, each with its reason: the Discord webhook secret
reference (HardcodedPasswords), escaped `]` / `}` in regexes, the
`@i18n/index` imports tsconfig needs, the three react-hooks warnings
eslint.config.js documents, the legacy `@deprecated` draft fields in the
files that migrate them; in src-tauri/qodana.yaml the module paths
`generate_handler!` needs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A Qodana workflow with one job per Qodana Cloud project:
- typescript: Qodana for JS in native mode, on the runner's Node 26 and
node_modules (qodana.yaml, project yt-ts-js, QODANA_TOKEN_TS_JS);
- rust: Qodana for Rust, Early Access, in Docker on src-tauri/
(src-tauri/qodana.yaml, project yt-rust, QODANA_TOKEN_RUST). Its
bootstrap installs what rust.yml installs; a stand-in dist/index.html
lets generate_context!() expand.
Both use qodana.recommended with a quality gate of zero problems and
analyse the whole project on every run. A tokens job skips the analysis
for Dependabot and fork PRs, which get no secrets; the token reaches only
the scan step, never `npm ci`. Annotations and artifacts, no PR comment.
Failures reach Discord through notify-ci-failure.yml.
Docs: TECH-SPEC (workflow table, Qodana notes), DEVELOPMENT (+ vi),
CONTRIBUTING, CLAUDE.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
npm, the newest releases published before 2026-11-10 (the same 7-day
cooldown Dependabot uses): react-i18next 17.1.13, lucide-react 1.70,
zustand 5.1.0, simple-icons 16.37, vite 8.3.7 (rolldown 1.2.18),
@vitejs/plugin-react 6.3.0, tailwindcss and @tailwindcss/postcss 4.3.5,
typescript-eslint 8.72.2, knip 6.44.2, and the exact pins marked 18.2.0
and wrangler 4.159.0 (miniflare 5.20261109.0-beta, workerd 1.20261109.1).
THIRD_PARTY_NOTICES regenerated. No lock entry moved backwards.
Rust: async-executor 1.14.0 -> 1.14.1. 1.14.0 was yanked, and the weekly
cargo-deny run warned about it.
Held back, still inside the cooldown: eslint 10.15 / typescript-eslint
8.73 (they move to minimatch 11, the fix for the medium, dev-only alert
#50) and Tauri 2.12.6.
Closes#251, #252, #253, #255, #256.
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>
Folds Dependabot's #242, #243, #244, #246 and #247 into one change.
Each failed the required `check` job the same way (a new version makes
THIRD_PARTY_NOTICES.md stale) and they conflict with each other in
package-lock.json and the notices.
npm, installed with `npm update --before=2026-11-03`, the 7-day
cooldown Dependabot uses:
- i18next 26.5.11 -> 26.6.0, react-i18next 17.1.9 -> 17.1.11,
i18next-resources-to-backend 1.2.3 -> 1.2.4
- lucide-react 1.64.0 -> 1.66.0, react-router-dom 7.18.4 -> 7.18.5,
simple-icons 16.35.0 -> 16.36.0
- vite 8.3.4 -> 8.3.5 (rolldown 1.2.16), @vitejs/plugin-react 6.1.2 ->
6.2.1, tailwindcss 4.3.3 -> 4.3.4, postcss 8.5.32, autoprefixer
10.6.2, marked 18.1.1 -> 18.1.3
- eslint 10.13.0 -> 10.14.0, typescript-eslint 8.72.1, knip 6.44.1,
@types/node 26.6.6
- wrangler 4.152.0 -> 4.156.2 (miniflare 5.20261102.0-beta)
i18next stops at 26.6.x (`~26.6.0` plus a Dependabot ignore for
26.7.x): 26.7 adds the debug-mode warnings for the move to v27, about
1.9 KB gzip in the i18n chunk, which takes the initial load from 279.0
to 280.9 KB, over the 280 KB budget, for code the app never runs.
The undici override is gone: miniflare 5.20261102.0-beta depends on
undici 7.30.1 itself (alert #49 stays fixed).
Rust: tauri 2.12.4 -> 2.12.5, tauri-build / -macros / -codegen 2.7.4,
tauri-runtime-wry 2.12.3, wry 0.57.1, tao 0.37.2, tauri-plugin-dialog
2.8.4 (rfd 0.17), tauri-plugin-single-instance 2.5.5. All older than
the cooldown. THIRD_PARTY_NOTICES regenerated.
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>
- Colour tokens reach WCAG AA: lighter muted text and accent in the dark
theme, darker muted/success/warning/danger/donate in the light theme, and
new accent-solid / danger-solid fills for buttons with white text.
tests/styles/contrast.test.ts checks every text token on every surface.
- Generated text carries its language (lang) on Output, the YouTube and
quick previews, History, Batch, Social and Playlist, so screen readers read
Japanese output with a Japanese voice.
- RouteAnnouncer reads the new page's name after a navigation; focus stays.
- Toast region and close button are translated; Alt+T is in the shortcut list.
- Endings table inputs and the custom bank name get accessible names; the
From/To headers are translated.
- Settings > Editor > Single-key shortcuts turns the bare ? off (WCAG 2.1.4).
- Text inputs use outline-hidden so the focus outline shows in Windows High
Contrast; the genre remove button is 24px, small close/dismiss buttons
grow on touch screens.
- Desktop: zoomHotkeysEnabled (Ctrl/Cmd + = / -), with the
set-webview-zoom permission for the macOS/Linux polyfill.
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>
Video settings gain "Upscaled from" next to Resolution: footage recorded
at 1440p and exported at 4K in the video editor is now declared as such.
- Title: the quality badge reads "[4K Upscaled]" ("[2K Upscaled]",
"[4K Upscaled 120FPS]"), with the word in the output language; badge
position, case and the "Show quality badge" setting apply as before.
1080p 60fps keeps no badge, upscaled or not.
- Description, VIDEO SETTINGS: "Upscale: 1440p → 4K (DaVinci Resolve
Studio 21.2)" right under the Video line, the editor taken from My Rig.
It stays when the graphics settings are hidden.
- Description, TECH NOTES: an automatic bilingual note that upscaling
reconstructs fine detail, so text, textures and edges may look slightly
different from the original image. It is not in the checklist and
goes away with the upscale.
- The Select lists only resolutions below the video's; lowering the
resolution to or below the source ends the upscale. The collapsed
section reads "1440p → 4K · 60 FPS". Saved with the channel profile.
- Editor store v20 → v21 (back-fills "" and drops unknown values);
backups and applied items read an unknown value as not upscaled.
`validUpscaleSource` in src/engine/upscale.ts is the one rule the
title, description and form share. AUTO_TECH_NOTES holds the engine's
own notes; their bullets share description.techNotes.items.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GitHub retired the macOS 14 runner image on 2026-11-02. The v1.4.0 tag's
Release Desktop run had its macOS job cancelled before any step ran
("The configuration 'macos-14-arm64-us-default' is not supported"); the
Windows and Linux builds went through. macos-15 is the direct Apple
silicon successor.
The macOS .app.tar.gz for v1.4.0 will come from the workflow's manual
`workflow_dispatch` re-run with tag v1.4.0, which takes the job matrix
from main and checks out the tag's code. PACKAGING's runner table and
the v1.4.0 CHANGELOG entry say so.
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>
Folds #223-#227 into one change. Each of them failed the required
`check` job the same way: a new version makes THIRD_PARTY_NOTICES.md
stale, and merged one by one they would conflict with each other in
package-lock.json and the notices.
- i18next 26.5.3 -> 26.5.11, react-i18next 17.1.0 -> 17.1.9
- lucide-react 1.59.0 -> 1.64.0, zustand 5.0.15 -> 5.0.16
- knip 6.42.1 -> 6.44.0
- wrangler 4.151.2 -> 4.152.0 (miniflare 5.20261019.2-beta)
- @tauri-apps/cli 2.12.3 -> 2.12.4 (matches the tauri 2.12.4 crate)
Installed with `npm install --before=2026-10-30`, the same 7-day
cooldown Dependabot uses; lucide-react and knip land on the newest
releases past it (1.64.0, 6.44.0) rather than Dependabot's 1.61.0 and
6.43.0. The undici override stays: miniflare 5.20261019.2-beta still
pins undici 7.29.1. THIRD_PARTY_NOTICES regenerated.
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>
Two Workers Rate Limiting bindings in wrangler.jsonc, checked first in
the router so a flood costs no siteverify call, HMAC check or asset
fetch:
- RATE_LIMIT: 120 requests a minute for everything the Worker handles
(gate page, app shell, legal pages, /__gate/*, any method).
- VERIFY_RATE_LIMIT: 10 a minute for POST /__gate/verify on top.
Clients are keyed by IPv4 address or IPv6 /64. Over the limit: 429 with
Retry-After: 60 (plain text, or JSON for the verify call). Like the
gate, it fails open when a binding is missing or limit() throws, and
logs that once per isolate. A test keeps wrangler.jsonc's bindings and
period in step with the code.
HOSTING documents both layers and the zone's WAF rate limiting rule
(Free plan: one rule, per IP, 10 s) as the first one.
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>
- undici 7.30.1 through `overrides` (alert #49, GHSA-xjj6-f33q-929c,
dev only): miniflare pins undici exactly, so Dependabot's security
job fails with security_update_not_possible. The note in
dependabot.yml says when to drop the override.
- npm, newest releases at least seven days old (the Dependabot
cooldown): react + react-dom 19.3.1, i18next 26.5.3,
react-i18next 17.1.0, lucide-react 1.59.0, simple-icons 16.35.0,
eslint 10.13.0, typescript-eslint 8.72.0, knip 6.42.1,
postcss 8.5.31, @types/node 26.6.5, wrangler 4.151.2
- tauri crates to match @tauri-apps/api 2.12.4: tauri 2.12.4,
tauri-build 2.7.3, tauri-plugin-dialog 2.8.3, -opener 2.7.2,
-single-instance 2.5.4, -fs 2.7.1
- THIRD_PARTY_NOTICES regenerated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>