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>
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>
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>
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>
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>
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>
- 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>
SonarCloud's Automatic Analysis is off. The new `sonarcloud` job in
ci.yml runs SonarSource/sonarqube-scan-action v8.3.0 after `check`, with
the LCOV report that `check` now uploads; it never installs npm packages,
so SONAR_TOKEN never shares a job with them, and it fails with the
quality gate. Fork and Dependabot PRs skip it (no repository secrets).
sonar-project.properties analyses the tests as tests, imports the
coverage and excludes from it everything Vitest does not measure. Vitest
now also measures src/config, src/store and src/utils, next to the
engine, the Worker and the build plugins. The job passes package.json's
version as sonar.projectVersion, so the "previous version" new-code
period starts again at every release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Regexes with super-linear backtracking (S8786 x16) are rewritten to stay
linear on long runs; each new pattern gives the same results as the old one
on 150k-450k fuzzed inputs (except where noted) and finishes adversarial
50k-character inputs in under 3 ms:
- tag-generator QUALIFIER_SUFFIX_RE starts just before a `:`/space run
(`(^|[^:\s])…` + "$1"), never inside one
- timeline-parser matches `line.trimEnd()` with a greedy label, and renders
with trimEnd(); cleanCpuName collapses whitespace before the patterns
- editor-store endings, Google Play urlPattern (lookahead for `id=`),
channel-phrase punctuation, SPDX OR/AND split, legal-docs slug and link
stripping (link text/URL may not contain `[`), base64url padding, and a
loop for trailing slashes in the worker router
Others:
- S2871: sorts take the shared code-unit comparator (same order as before;
THIRD_PARTY_NOTICES is unchanged)
- S4822: ErrorBoundary catches the logger import with .catch(), which a
try/catch never could
- S3516: migrateProfilesState returns a new object
- S7773: Number.parseInt (x10)
- S9379: Modal takes an initialFocusRef (Radix onOpenAutoFocus), so the
shortcut search box gets focus without an autoFocus attribute
- S2245: generateId drops the Math.random fallback; getRandomValues exists
everywhere the app runs, and a non-random ID is worse than an error
- S4036: NOSONAR on the dev script's `git` call (PATH lookup by design)
- S6505/S8543: every workflow installs with `npm ci --ignore-scripts`, and CI
runs `npm run cf:check` instead of `npx wrangler …`
- S6358: Android sets allowBackup="false" — app data is no longer copied to
Google Drive backups; Backup & Restore moves it to a new phone
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
TypeScript 7.0 is the native compiler and ships no JavaScript API, which
typescript-eslint still needs. Install both, as Microsoft documents it:
- "@typescript/native": "npm:typescript@^7.0.2" gives `tsc` = 7.0
- "typescript": "npm:@typescript/typescript6@^6.0.2" gives the 6.0 API
that typescript-eslint loads (its peer range stops below 6.1), and `tsc6`
CI fails if `tsc` ever resolves to TypeScript 6 (@typescript/old, pulled in
by the 6.0 package, ships a `tsc` too).
tsconfig.json (src):
- target ES2025: the newest year TypeScript 7.0, esbuild and Vite all know
- lib ES2022 + DOM: the browser floor (Vite's baseline-widely-available,
Chrome 111 / Safari 16.4 / Firefox 114), because nothing polyfills
- baseUrl removed (gone in 7.0; paths were already relative), DOM.Iterable
dropped (merged into DOM), `types: []` spelled out, erasableSyntaxOnly and
verbatimModuleSyntax on (both clean)
tsconfig.check.json: lib ES2025 for tests, scripts, worker and build plugins.
Platform floor: the Tauri build no longer lowers to es2020; it shares the
web build's baseline (the stylesheet already needed Chromium 99+ /
Safari 15.4+). macOS minimumSystemVersion is 11.0 (the build is arm64).
Also: eslint.config.js uses ESLint's defineConfig (tseslint.config is
deprecated); THIRD_PARTY_NOTICES names the real package behind an npm
alias, sorted with a shared code-unit comparator (src/utils/sort.ts);
Dependabot groups typescript + @typescript/*; a test's typed-array
annotation follows TypeScript 7's lib.dom.
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>
Every notice already says 2026, which is right: the first commit is from
2026-04-07, so there is no 2025 to fix and no 2025-2026 range to claim.
What was missing is anything keeping the years current.
- src/config/brand.ts: COPYRIGHT_START_YEAR and copyrightYears(), "2026"
now and "2026-2027" from the first commit made in 2027
- npm run check:copyright (CI, next to check:licenses) holds NOTICE,
REUSE.toml and the installers' copyright string to HEAD's commit year,
not the clock, so old commits stay green; npm run update:copyright
rewrites them
- tauri.conf.json gains bundle.copyright, so the .exe/NSIS, macOS and
Linux packages stop shipping an empty copyright field
- the /legal pages' footer prints the same range at build time
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
workflow-lint started failing on every pull request: zizmor reports
impostor-commit for dtolnay/rust-toolchain@6bed076 (# stable). The
action's `stable` branch is regenerated from master (last on 2026-10-01),
so the commit pinned from it no longer belongs to the repository's
history, and the `# stable` comment no longer matches either.
Pin 7e38f4b, the current master head (the regenerated `stable` is that
commit plus a default toolchain), in rust.yml and both release workflows.
Master keeps its history, and every step already passes
`toolchain: stable`, which master's action.yml requires.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- CHANGELOG: the v1.0.0 entry (moving house, new interface, data fixes,
backup & restore, faster entry, catalogs, desktop hardening, CI).
- README: the web app at ytgenerator.stream, what moved from GitHub
Pages, current features, privacy as it is now (Cloudflare delivery,
Turnstile, cookieless analytics on the web only), contacts by purpose;
the dead Discord invite and the old email are gone.
- docs/HOSTING.md (new): Worker routing, cookies, headers, secrets,
one-time dashboard settings, local dev, previews and rollback.
- CLAUDE.md rewritten for the real stack, layout, commands and rules.
- CONTRIBUTING / PR template / issue templates: main-only branching,
the required checks, 8 locales, Android and current versions; issue
links to security advisories, the wiki, Discord and poli0981.dev/links.
- DISCLAIMER (+ Vietnamese), NOTICE: current model disclosure and the
copyright / DMCA contacts. PRIVACY: backup locations and the moving
notice on the old address.
- Version 1.0.0 in package.json, package-lock.json, tauri.conf.json,
Cargo.toml and Cargo.lock.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
poli0981.github.io/youtube-generator still serves v0.38 to old bookmarks,
and the data people saved there can't follow to ytgenerator.stream on its
own (browser storage belongs to a site). A single static page replaces it:
- reads the ytdescgen-* stores this browser saved on the old address and
downloads them as a backup file in the new format (Settings › Restore
reads it: migrations, the preview and Undo apply as for any backup);
- points to ytgenerator.stream, in English or Vietnamese;
- noindex, canonical to the new site, and a 404 copy for old deep links.
pages-migration.yml deploys it by hand (workflow_dispatch, pinned
actions, job-scoped permissions). The page, the workflow and the
github-pages environment go on 2026-11-29.
A regression test feeds the page's exact output through the restore.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
zizmor (workflow-lint) flagged three things:
- cache-poisoning: setup-node v7 restores the npm cache unless told not
to, and the release workflows publish what they build. They now set
`package-manager-cache: false`, so a cache written by another workflow
can never reach a release artifact.
- dependabot-cooldown: raise every ecosystem to 7 days.
- dangerous-triggers: the two `workflow_run` notifiers are ignored with
the reason in zizmor.yml; the shared workflows only read run metadata
and pass untrusted fields through `env:`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New checks
- security.yml: dependency-review blocks PRs that add a high/critical
advisory; actionlint + zizmor lint the workflows themselves (template
injection, permissions, credential persistence, unpinned uses); OpenSSF
Scorecard weekly and on main (published, not uploaded as alerts).
- compliance.yml: REUSE lint over the whole repo (REUSE.toml + LICENSES/,
no per-file headers) and Conventional-Commit PR titles.
- rust.yml (src-tauri changes + weekly): rustfmt, clippy -D warnings,
cargo test, and cargo-deny for RustSec advisories, licenses and sources.
- ci.yml `check` gains: coverage thresholds (src/engine, worker),
check:licenses, check:bundle, and a `wrangler deploy --dry-run`.
Licensing
- THIRD_PARTY_NOTICES.md is now generated from package.json, the installed
packages and Cargo.toml/Cargo.lock (`npm run generate:third-party`); CI
fails when it is stale or when anything bundled into the app carries a
license outside the allowlist. It had drifted to React 18 / Vite 7 /
Tailwind 3.
- Vite's build.license emits the full text of every bundled package's
license to /licenses/third-party.md (served publicly, before the gate).
Bundle budget
- scripts/check-bundle-size.ts measures what CLAUDE.md's "500KB" never
defined: initial load (everything index.html references) <= 280 KB gzip
(197 KB today) and no JS chunk over 500 KB raw.
Coverage
- @vitest/coverage-v8; thresholds sit just under today's numbers. The
engine is at 89% lines / 64% functions — not the 100% CLAUDE.md claimed.
Supply chain
- Every third-party action pinned to a commit SHA (Dependabot updates the
SHA and its version comment); checkout never persists credentials.
- Release workflows: a `verify` job (typecheck, tests, version sync, Tauri
alignment, tag == package version) gates the build; no dependency caches
in release jobs; permissions granted per job.
- Reusable Discord workflows receive only the secrets they declare instead
of `secrets: inherit` (which exposed the Android signing keys to them).
- Rust: cargo-deny found RUSTSEC-2026-0194/0195 (quick-xml DoS, via plist)
that Dependabot had not raised; plist 1.10 brings quick-xml 0.41.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One lockfile instead of nine PRs: every minor/patch the open Dependabot PRs
proposed, plus everything else that moved within range.
npm (`npm update --save`)
- react/react-dom 19.3, vite 8.3, i18next 26.4, react-i18next 17.0.15,
react-router 7.18.4, eslint 10.11, typescript-eslint 8.71, knip 6.38,
prettier 3.9.9, @vitejs/plugin-react 6.1, @tauri-apps/* 2.12 / plugins,
@types/*, @testing-library/react, postcss, autoprefixer, tsx.
- Security: vitest + @vitest/mocker 4.1.11 (path traversal via redirect
mock), @humanfs/node 0.16.8 (symlinked copy). `npm audit`: 0.
- Majors stay out (TypeScript 7, Vitest 5, lucide-react 1).
Rust (`cargo update -p tauri …`)
- tauri 2.12, tauri-build 2.7, dialog 2.8, fs 2.6, opener 2.7, shell 2.4,
single-instance 2.5 — matching the npm side minor for minor.
- tauri 2.12 no longer depends on kuchikiki, so `rand` 0.7.3 (the unsound
custom-logger advisory) leaves Cargo.lock entirely. Only glib 0.18 (gtk-rs
0.18 Linux stack) remains ignored.
CI and config
- New `npm run check:tauri`: the tauri CLI refuses to build when the npm
packages and crates differ in major.minor, and CI never runs `tauri build`
— so a one-sided bump merged green and broke the next release tag. Now CI
says which side lags.
- dependabot.yml: 3-day cooldown for version updates (security updates are
exempt), new ui / cloudflare / testing / types groups, rand ignore removed.
- actions/setup-java v5 -> v6 (release-android).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Worker connected to ytgenerator.stream was serving a build made for the
GitHub Pages sub-path: index.html asked for /youtube-generator/assets/*.js, the
SPA fallback answered every one of those with index.html, and the site loaded
blank. Both builds are now served from `/`.
- vite.config.ts: base "/" for web and Tauri alike.
- wrangler.jsonc: the one Cloudflare file in the repo. Assets-only for now
(dist/, SPA fallback, custom domain declared so `wrangler deploy` never
detaches it, workers.dev off, build.command runs `npm run build`).
- public/_headers: CSP, nosniff, Referrer-Policy, Permissions-Policy, COOP,
X-Frame-Options; immutable caching for hashed /assets/*. No HSTS - the
zone edge already sends it with preload.
- index.html, manifest, robots, sitemap: canonical/OG/JSON-LD on the new
domain, pt-BR and id added to the locale metadata, Android listed.
- Brand: one SVG source in assets/brand/ now drives the favicon, the PWA
icons (192/512/maskable), apple-touch-icon, a 1200x630 link-preview card
and every Tauri desktop/Android/iOS icon. The desktop and Android apps had
been shipping a flat indigo placeholder square; manifest and index.html
pointed at four PNGs that did not exist. `npm run generate:brand`
re-renders the web images; the Android adaptive icon gets a glyph-only
foreground on the brand colour instead of a tile on a white disc.
- deploy-web.yml and notify-deploy.yml removed, .nojekyll dropped. The last
Pages deployment stays online untouched until the data-migration page
replaces it.
- .node-version pins Node 22 for Workers Builds; wrangler, @tauri-apps/cli
and @resvg/resvg-js are pinned dev dependencies (`npm run cf:dev`,
`npm run cf:check` for a dry-run deploy).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The v0.35.0 APK built successfully three times and was never attached. The
build was fine every time; the upload step failed with "Resource not accessible
by integration" on update-a-release.
`softprops/action-gh-release@v3` was resolving the target release from
GITHUB_REF rather than from the `tag_name` it was handed. On the tag push it
looked for a release tagged `refs/tags/v0.35.0`; on the workflow_dispatch re-run
it looked for one tagged `refs/heads/main`. Neither exists, so it fell through
to CREATING a release against a branch ref, which the token is quite right to
refuse. The permissions were never the problem — the job log shows
`Contents: write` on every run.
Replaced with `gh release upload`, which is pre-installed on every runner and
takes the tag as a positional argument, so it cannot make that substitution.
`--clobber` makes a re-run idempotent.
Also uploads the APK as a workflow artifact first, so a failed release upload
never costs another 20-minute NDK build to recover from — which is what it cost
to diagnose this.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
CI ran typecheck/lint/locales/test/build. Everything else the repo owned was
configured but never executed — `knip` was installed and configured yet ran
nowhere, Prettier had a config and no gate, and the six version fields the
release ritual bumps by hand had nothing watching them. This wires all of it
into the pipeline.
Correctness gaps this immediately caught:
- `tsconfig.json` covers only `src`, so tests/ and scripts/ were NEVER
type-checked. Adding `tsconfig.check.json` (+ `typecheck:all`) surfaced 53
errors, including three fields silently missing from the editor→engine
parity fixture: `videoStyleEra` (v0.22.0), `adEmail` + `gameKeyEmail`
(v0.34.0), and the four `endings*` fields (v0.16.0/v0.17.1). The fixture is
the guard against exactly that class of drift, and it had drifted itself.
- `vitest.config.ts` `include` matched only `*.test.ts`, so any `.test.tsx`
would have been collected by nobody and "passed" silently. Now `{ts,tsx}`.
New gates in ci.yml: `typecheck:all`, `format:check`, `knip`, `check:version`,
and an advisory `npm audit --audit-level=high` (advisory so a fresh transitive
advisory cannot redden every unrelated PR before Dependabot opens its fix).
Plus least-privilege `permissions: contents: read` — which also clears the
`actions/missing-workflow-permissions` code-scanning alert — and a
concurrency group that cancels superseded runs everywhere except `main`.
New scripts:
- `scripts/check-version-sync.ts` — asserts all SIX version fields agree
(package.json, package-lock root AND packages[""], tauri.conf.json,
Cargo.toml, Cargo.lock self-entry). Nothing else notices a missed one, and a
stale tauri.conf.json ships an installer that disagrees with its tag.
- `scripts/generate-locale-template.ts` — `npm run generate:locale` has been
advertised in package.json and docs/I18N.md step 1 since v0.1, but the file
was never committed, so the documented first step of adding a language
failed outright. Blocks the planned pt-BR + id work.
Dead code removed: the Rust `ensure_dir` command and its two scoped `opener:`
capabilities. Its documented caller, `openSettingsFolder()`, no longer exists
in `src/` — `opener:default` (all `openExternal` needs) is untouched. Also
`@tauri-apps/plugin-opener` left knip's ignore list now that it is genuinely
imported, and `DroppedReasonId` went from unused export to typing
PlaylistPage's dropped-reason state.
Security: the `js/incomplete-url-substring-sanitization` alert in
description-builder.test.ts was a real (if low-stakes) weak assertion —
`includes("itch.io")` also matches `https://itch.io.example.com/`, so the
test could pass on the wrong line. Now matches the full URL.
CHANGELOG: v0.31.0, v0.32.0 and v0.32.1 shipped as tagged releases but were
never logged, leaving the file jumping v0.33.0 → v0.30.0. Reconstructed from
the release commits in the file's existing house style.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
GitHub deprecated the Node.js 20 Actions runtime on 2026-06-16 (removal
from runners 2026-09-16). release-android.yml was the only workflow still
pinning actions whose latest-supported runtime was node20; each has a
newer major declaring `runs.using: node24`, so bump to the floating major:
actions/setup-java v4 -> v5 (node20 -> node24)
android-actions/setup-android v3 -> v4 (node20 -> node24; defaults
cmdline-tools 20.0, NDK install
via sdkmanager unaffected)
actions/cache v4 -> v5 (node20 -> node24)
softprops/action-gh-release v2 -> v3 (node20 -> node24)
All four bumps are pure runtime migrations with unchanged inputs. The
node24 majors require Actions Runner >= 2.327.1, which GitHub-hosted
ubuntu-latest already satisfies. ci.yml and release-desktop.yml use only
checkout@v6 / setup-node@v6 (already node24) plus composite actions
(rust-toolchain, tauri-action) that have no Node runtime, so no changes
there. App build node-version (22) is unaffected — this is action
runtimes only. Verified with actionlint (clean) + YAML parse.
Co-Authored-By: Claude Opus 4.8 <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>
Node 20 reached end-of-life in April 2026 and GitHub is removing it
from runner images (actions/runner-images#14029), so setup-node now
downloads it on every run. Node 22 satisfies Vite 7's engine range
(^20.19 || >=22.12) and matches the docs/TECH-SPEC.md snippets.
Also sync the two doc mentions of CI's Node version.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Build-only run 27388695090 on windows-2025-vs2026 produced both MSI
and NSIS bundles cleanly, so windows-latest stays unpinned.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
windows-latest redirects to this image from June 15, 2026. Build-only
(no tagName), so no release is touched. Reverted before merge.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
GitHub forces the Node 24 runtime for actions on June 16, 2026 and
removes Node 20 from runners September 16, 2026. checkout v4,
setup-node v4, configure-pages v5, upload-pages-artifact v3 and
deploy-pages v4 all declare node20; their current majors (v6/v6/v6/
v5/v5) declare node24. tauri-action@v0 already runs node24 and
dtolnay/rust-toolchain is composite, so both stay.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Dependabot cargo security-update jobs for rand and glib fail with
security_update_not_possible every time Cargo.lock changes on main
(runs 27387346373, 27387346324). Both are transitive deps of tauri:
rand 0.7.3 is pinned to ^0.7 by phf_generator 0.8 (via kuchikiki),
fix is 0.8.6; glib 0.18.5 is pinned by the gtk-rs 0.18 stack, fix is
0.20.0. Cargo cannot resolve the patched versions until tauri bumps
those subtrees, so ignore both to stop the recurring red runs.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
v0.24.1's Linux job failed on a sustained upstream GitHub-CDN 504 while the AppImage bundler fetched linuxdeploy, so v0.24.1 shipped with only Windows + macOS binaries. Set APPIMAGE_EXTRACT_AND_RUN=1 + NO_STRIP=true on the tauri-action step (fixes the linuxdeploy FUSE run-failure mode + future resilience; no-op on Win/macOS) and bump to 0.24.2 to re-run the full matrix. No application code changes — identical app to v0.24.1.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- workflows: narrow notify-* triggers to specific producer names so non-matching
workflow_run events don't instantiate a run (kills the Actions tab Skipped spam)
- workflows: auto-link each published release to a GitHub Discussion under
Announcements via a new link-discussion job before the Discord announce
- repo: add FUNDING.yml + ISSUE_TEMPLATE/{config,bug_report,feature_request}.yml
- docs: add docs/pc_spec.md, docs/dev_env.md (+ VI mirrors) and webapp/TAURI.md
- about: restructure AboutPage with Donate / Dev Environment sections, expanded
socials (Bluesky, Mastodon, Steam, Telegram bot+user, email, game Discord);
Ko-fi / Patreon moved from ABOUT.socials to new @config/donate
- header: persistent Donate button (Ko-fi) left of the language switcher
- sidebar: external Report Bug item linking directly to the bug_report template
- seo: full <head> metadata (description, OG, Twitter card, JSON-LD
WebApplication, 6 locale alternates), per-route useDocumentTitle hook applied
to all 9 pages, robots.txt, sitemap.xml, manifest.webmanifest, placeholder
favicon.svg
- warnings: new "horror_specific" group with 7 IDs (eye_horror, body_horror,
face_horror, cosmic_horror, extreme_gore, decay_rot, mutilation), localized
to en/vi/ja/es/ko/zh in both ui.json and templates.json
Additive only — no breaking changes to the engine, store schema, or persisted
content-warning IDs. _schema.json updated to reflect new keys.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>