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>
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>
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 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>
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>