github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 15:12:35 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[PR #1309] [MERGED] Fix ID for transaction_filters migration, patch existing migration #38092

New Issue
Closed
opened 2026-04-23 11:14:14 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-23 11:14:14 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/1309
Author: @j-f1
Created: 7/7/2023
Status: ✅ Merged
Merged: 7/8/2023
Merged by: @j-f1

Base: master ← Head: jed/fix-migration

📝 Commits (4)

  • a3f8092 Fix ID for transaction_filters migration, patch existing migration at runtime
  • 8dc32df Persist migration update
  • 6c94848 Add release note
  • 7b7936e Update packages/loot-core/src/server/migrate/migrations.ts

📊 Changes

3 files changed (+21 additions, -0 deletions)

View changed files

📝 packages/loot-core/migrations/1688749527273_transaction_filters.sql (+0 -0)
📝 packages/loot-core/src/server/migrate/migrations.ts (+15 -0)
➕ upcoming-release-notes/1309.md (+6 -0)

📄 Description

I gave this a small test (running the commit before the filters PR was merged, then this commit) and it seems to be fine. Would like to see some others give it a try too though.

🔄 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/1309 **Author:** [@j-f1](https://github.com/j-f1) **Created:** 7/7/2023 **Status:** ✅ Merged **Merged:** 7/8/2023 **Merged by:** [@j-f1](https://github.com/j-f1) **Base:** `master` ← **Head:** `jed/fix-migration` --- ### 📝 Commits (4) - [`a3f8092`](https://github.com/actualbudget/actual/commit/a3f80921ccc73d3130b5b1a0f2203ed7fe29af72) Fix ID for transaction_filters migration, patch existing migration at runtime - [`8dc32df`](https://github.com/actualbudget/actual/commit/8dc32df197dbc5bfb2cb26db756ec492a62f7031) Persist migration update - [`6c94848`](https://github.com/actualbudget/actual/commit/6c9484854a22567c9ac2c7d5d0b98114c1f64459) Add release note - [`7b7936e`](https://github.com/actualbudget/actual/commit/7b7936e3c35f2f518e753c4c4673fb92a06f60b7) Update packages/loot-core/src/server/migrate/migrations.ts ### 📊 Changes **3 files changed** (+21 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/loot-core/migrations/1688749527273_transaction_filters.sql` (+0 -0) 📝 `packages/loot-core/src/server/migrate/migrations.ts` (+15 -0) ➕ `upcoming-release-notes/1309.md` (+6 -0) </details> ### 📄 Description I gave this a small test (running the commit before the filters PR was merged, then this commit) and it seems to be fine. Would like to see some others give it a try too though. --- <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-04-23 11:14:14 -05: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#38092
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?