fix tmp cve override #17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "lavender/address-cve-tmp@0.2.5"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
summary
this addresses forgejo issue #15 by moving the root
tmpoverride past the vulnerable range and refreshing the bun lockfile. bun now resolves the electron forge packaging chain totmp@0.2.7.validation
bun auditreports no vulnerabilities.bun why tmpshowsexternal-editorresolving totmp@0.2.7through the desktop packaging chain.bun testpasses with 250 tests.bun run checkstill reports pre-existing biome organize-import diagnostics in unrelated files, so i left that churn out of this security fix and documented it indocs/turns/2026-06-01-address-tmp-cve.html.intended effect for end users
users should not see any product behavior change. the intended effect is cleaner dependency posture for desktop packaging and developer installs: the repository lockfile no longer carries the flagged
tmp@0.2.5entry from cve-2026-44705.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.