-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
⬆️ bump adm zip to 0.5.16 #5019
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for actualbudget ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Bundle Stats — desktop-clientHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Bundle Stats — loot-coreHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger
Smaller No assets were smaller Unchanged No assets were unchanged |
This is annoying when the Netlify build gets stuck. Maybe #5014 will help
|
WalkthroughThe dependency "adm-zip" in the loot-core package.json file was updated from version 0.5.10 to a patched version 0.5.16 using Yarn's patch protocol. This change replaces the direct version reference with a reference to a local patch file for version 0.5.16. No other dependencies or configurations were modified, and there were no changes to exported or public entities. Suggested labels
Suggested reviewers
Note ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. Note ⚡️ Faster reviews with cachingCodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure 📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (14)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
package.json (1)
75-75
: Document patch-package usage for contributors
Includingpatch-package
(^8.0.0
) is on point. Consider updating CONTRIBUTING.md or developer docs to explain how to create, apply, and update patches underpatches/
.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (2)
upcoming-release-notes/5019.md
is excluded by!**/*.md
yarn.lock
is excluded by!**/yarn.lock
,!**/*.lock
📒 Files selected for processing (3)
package.json
(2 hunks)packages/loot-core/package.json
(1 hunks)patches/adm-zip+0.5.16.patch
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (5)
- GitHub Check: Visual regression
- GitHub Check: Functional
- GitHub Check: build (windows-latest)
- GitHub Check: build (macos-latest)
- GitHub Check: build (ubuntu-latest)
🔇 Additional comments (4)
packages/loot-core/package.json (2)
26-26
: Bump adm-zip to latest patch version
Updating adm-zip from^0.5.10
to^0.5.16
incorporates critical fixes (Linux permissions, Windows path handling, async folder support, zip bomb protection, etc.) as intended by this PR.
26-26
: Verify integration after the bump
Please run the suite of unit/integration tests—or add new ones—to confirm zip-related functionality inloot-core
behaves correctly with the new version and applied patch.package.json (1)
53-55
: Ensurepatch-package
postinstall runs smoothly
Adding"postinstall": "patch-package"
applies local fixes automatically. Verify this hook executes correctly under Yarn v4 (Plug’n’Play) and doesn’t conflict with existing lifecycle scripts (e.g.,prepare
).patches/adm-zip+0.5.16.patch (1)
7-7
: Adopt optional chaining and nullish coalescing
Switching toprocess?.versions?.node ?? ""
guards against undefinedprocess
orversions
, preventing runtime errors. This aligns with modern JS best practices given our Node ≥20 target.
I've split this out from #5015 because adm-zip requires patching.
I've had a PR up there (cthackers/adm-zip#551) for quite a while but no response yet so this is the only way to update without changing the dependency over.
adm-zip (0.5.10 → 0.5.16)