github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #55] [MERGED] Lock packages to the versions for which patches have been made #2993

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

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/55
Author: @TomAFrench
Created: 5/7/2022
Status: ✅ Merged
Merged: 6/29/2022
Merged by: @jlongster

Base: master ← Head: lock-packages

📝 Commits (2)

  • 7074c68 build: lock packages to the versions for which patches have been made
  • 87782e5 build: update react-modal in loot-design to 3.4.4

📊 Changes

4 files changed (+36 additions, -36 deletions)

View changed files

📝 packages/desktop-client/package.json (+3 -3)
📝 packages/loot-design/package.json (+3 -3)
📝 packages/mobile/package.json (+2 -2)
📝 yarn.lock (+28 -28)

📄 Description

I've been working to get a passing CI and noticed that the actual versions of the patched packages used have drifted from the versions that the patches target, causing the install step to fail. It seems like it's sensible to lock these down to an exact package version to avoid having to rebuild the patches unexpectedly.

The diff is a little messy but will become clearer if #46 is merged first.

Merging this along with #53 allows CI to install dependencies successfully.

🔄 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/55 **Author:** [@TomAFrench](https://github.com/TomAFrench) **Created:** 5/7/2022 **Status:** ✅ Merged **Merged:** 6/29/2022 **Merged by:** [@jlongster](https://github.com/jlongster) **Base:** `master` ← **Head:** `lock-packages` --- ### 📝 Commits (2) - [`7074c68`](https://github.com/actualbudget/actual/commit/7074c680d97d3355e344fcefab6dc4c0b9d05bac) build: lock packages to the versions for which patches have been made - [`87782e5`](https://github.com/actualbudget/actual/commit/87782e57ab904ce1576791a64dcc2ed27e4e80ce) build: update react-modal in loot-design to 3.4.4 ### 📊 Changes **4 files changed** (+36 additions, -36 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/package.json` (+3 -3) 📝 `packages/loot-design/package.json` (+3 -3) 📝 `packages/mobile/package.json` (+2 -2) 📝 `yarn.lock` (+28 -28) </details> ### 📄 Description I've been working to get a passing CI and noticed that the actual versions of the patched packages used have drifted from the versions that the patches target, causing the install step to fail. It seems like it's sensible to lock these down to an exact package version to avoid having to rebuild the patches unexpectedly. The diff is a little messy but will become clearer if #46 is merged first. Merging this along with #53 allows CI to install dependencies successfully. --- <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 20:34:44 -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#2993
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?