github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-08 12:59:01 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[PR #4412] [CLOSED] [WIP] bump deps to most recent patch versions #5369

New Issue
Closed
opened 2026-02-28 21:11:21 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:11:21 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/4412
Author: @matt-fidd
Created: 2/20/2025
Status: ❌ Closed

Base: master ← Head: bump-patch

📝 Commits (5)

📊 Changes

12 files changed (+1786 additions, -814 deletions)

View changed files

📝 package.json (+8 -7)
📝 packages/api/package.json (+6 -6)
📝 packages/component-library/package.json (+2 -2)
📝 packages/crdt/package.json (+4 -4)
📝 packages/desktop-client/package.json (+25 -25)
📝 packages/desktop-client/src/hooks/useLocalPref.ts (+7 -4)
📝 packages/desktop-electron/package.json (+3 -3)
📝 packages/eslint-plugin-actual/package.json (+1 -1)
📝 packages/loot-core/package.json (+13 -13)
📝 packages/sync-server/package.json (+13 -13)
➕ upcoming-release-notes/4412.md (+6 -0)
📝 yarn.lock (+1698 -736)

📄 Description

All worked smoothly here apart from adm-zip which breaks after 0.5.12 (only 4 patches behind latest though) because process.versions is set to {} instead of unset in the browser. I think it's caused by webpack but it's not the intended behaviour (adm-zip tries to guard against this for browser environments), I've opened https://github.com/cthackers/adm-zip/pull/551 upstream to fix.

This is prep for bumping more deps, but with the next ones being minor/major changes with potential breaking changes they'll be separated into more PRs.

Tested fairly thoroughly, I think if it gets through CI there should be minimal risk here.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/4412 **Author:** [@matt-fidd](https://github.com/matt-fidd) **Created:** 2/20/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `bump-patch` --- ### 📝 Commits (5) - [`2f79408`](https://github.com/actualbudget/actual/commit/2f79408d25f554457e2eaa0280fdf9d5fb485aa6) bump to latest patch - [`5b9e036`](https://github.com/actualbudget/actual/commit/5b9e036fc3f33350b22421f930936ae810acc898) adm-zip - [`a3e80b6`](https://github.com/actualbudget/actual/commit/a3e80b67802c97af7781af6e32a5976199fdd8e2) note - [`d3b37c6`](https://github.com/actualbudget/actual/commit/d3b37c6804ab25b78dc48c407e1686da48bafe58) fix useLocalPref typecheck error - [`6a46d92`](https://github.com/actualbudget/actual/commit/6a46d92a11525a39701ab52ed236d44b5fc4ecb3) pin types/react version for now ### 📊 Changes **12 files changed** (+1786 additions, -814 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+8 -7) 📝 `packages/api/package.json` (+6 -6) 📝 `packages/component-library/package.json` (+2 -2) 📝 `packages/crdt/package.json` (+4 -4) 📝 `packages/desktop-client/package.json` (+25 -25) 📝 `packages/desktop-client/src/hooks/useLocalPref.ts` (+7 -4) 📝 `packages/desktop-electron/package.json` (+3 -3) 📝 `packages/eslint-plugin-actual/package.json` (+1 -1) 📝 `packages/loot-core/package.json` (+13 -13) 📝 `packages/sync-server/package.json` (+13 -13) ➕ `upcoming-release-notes/4412.md` (+6 -0) 📝 `yarn.lock` (+1698 -736) </details> ### 📄 Description All worked smoothly here apart from `adm-zip` which breaks after `0.5.12` (only 4 patches behind latest though) because process.versions is set to `{}` instead of unset in the browser. I think it's caused by webpack but it's not the intended behaviour (adm-zip tries to guard against this for browser environments), I've opened https://github.com/cthackers/adm-zip/pull/551 upstream to fix. This is prep for bumping more deps, but with the next ones being minor/major changes with potential breaking changes they'll be separated into more PRs. Tested fairly thoroughly, I think if it gets through CI there should be minimal risk here. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 21:11:21 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#5369
Delete Branch "%!s()"

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?