Repository navigation
Conversation
Dependabot had open alerts against the app's lockfiles. This takes every fix that lands without a major version jump: - dompurify 3.4.17 and rustls 0.23.46, both shipped in the app - vite 7.3.7, vitest 4.1.12, happy-dom 21.0.4 and source-map-js 1.2.2, which only run at build and test time - postcss-selector-parser 6.1.5, forced through an override because @tailwindcss/typography pins 6.0.10 exactly Every version is past the 7-day dependency cooldown. The 354 frontend tests pass on happy-dom 21 and cargo check is clean. Left open: zip needs a major bump to 9 for both the app's own 2.x and the updater's 4.x, glib comes with the Linux GTK stack, rand 0.7 has no patched release, and deepmerge has no fix published. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
… bumps it needs Dependabot still had a critical and two other alerts open against zip. The fix is only in zip 9, and the app carries zip twice: its own 2.x for exporting and importing stash archives, and the updater plugin's 4.x for unpacking updates. - zip 2 -> 9.3.0. Entry names are now returned as a Result, so an archive with an unreadable name is refused with a message instead of being read. - tauri-plugin-updater 2.10 -> 2.14.1, the first release on zip 9. It needs tauri 2.12, so tauri goes 2.11.6 -> 2.12.5; the JS packages were already on 2.12.4 from the previous commit, so the crate and npm sides match again. - libc 0.2.191, which zip 9 requires. Cargo here is older than 1.100 and ignores the 7-day cooldown, so every crate new to the lockfile was checked against crates.io by hand, and seven that were under a week old (wry, toml and its family, winnow, brotli-decompressor) were pinned back to their previous release. The import path reads entries one by one through its own traversal check rather than zip's extract(), so the extraction bugs were not reachable; this removes them anyway. clippy is clean, 237 Rust and 354 frontend tests pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Every workflow pinned Node 22. The website moved to 24 with its Astro 7 upgrade, and this brings the app's test, release and screenshot jobs to the same line. Node 24 ships npm 11, which skips install scripts that are not approved. For this tree that is esbuild's binary check, whose platform binary arrives as an optional dependency anyway, and es5-ext's postinstall, which only prints a message. The local tree has been installed that way all along: tsc, the vite build and the 354 frontend tests pass on Node 24.21 with npm 11.19. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.