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 #1109] [MERGED] Fix migration ID for “remove account type” migration #3523

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

📋 Pull Request Information

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

Base: master ← Head: jed/fix-migration-number

📝 Commits (6)

  • 43471f7 Add check that newly added migration is the newest one
  • 8522d44 Update date on “remove account type” migration
  • edcd5dc Release note
  • 656da8e Update check.yml
  • 2af13e8 Use a more accurate detection script
  • 913f295 🔐

📊 Changes

4 files changed (+85 additions, -0 deletions)

View changed files

➕ .github/actions/check-migrations.js (+69 -0)
📝 .github/workflows/check.yml (+10 -0)
📝 packages/loot-core/migrations/1686139660866_remove_account_type.sql (+0 -0)
➕ upcoming-release-notes/1109.md (+6 -0)

📄 Description

Good catch @Jackenmen in https://github.com/actualbudget/actual/pull/948#issuecomment-1580501909 — I’ve also added a CI check to ensure bad migrations aren’t introduced in the future.

I think if you have a budget that has managed to have this migration applied successfully, you’ll need to manually patch getAppliedMigrations in packages/loot-core/src/server/migrate/migrations.ts and inject a query to remove the old migration ID and insert the new one.

🔄 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/1109 **Author:** [@j-f1](https://github.com/j-f1) **Created:** 6/7/2023 **Status:** ✅ Merged **Merged:** 6/8/2023 **Merged by:** [@j-f1](https://github.com/j-f1) **Base:** `master` ← **Head:** `jed/fix-migration-number` --- ### 📝 Commits (6) - [`43471f7`](https://github.com/actualbudget/actual/commit/43471f7ac080347329b528103c0f427027a045d6) Add check that newly added migration is the newest one - [`8522d44`](https://github.com/actualbudget/actual/commit/8522d44ab899b9a271911929abbc4407a74ec0d6) Update date on “remove account type” migration - [`edcd5dc`](https://github.com/actualbudget/actual/commit/edcd5dcd5a4fb940b2518268c3904731328e58fd) Release note - [`656da8e`](https://github.com/actualbudget/actual/commit/656da8e6c694ef6e11eda9f2a190baa298ee3ec4) Update check.yml - [`2af13e8`](https://github.com/actualbudget/actual/commit/2af13e82a14fd48a4e8d32aff4e958b21e33ae7c) Use a more accurate detection script - [`913f295`](https://github.com/actualbudget/actual/commit/913f295d8cc06e02f69bb8f8e6c2b7484eb8927e) 🔐 ### 📊 Changes **4 files changed** (+85 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/actions/check-migrations.js` (+69 -0) 📝 `.github/workflows/check.yml` (+10 -0) 📝 `packages/loot-core/migrations/1686139660866_remove_account_type.sql` (+0 -0) ➕ `upcoming-release-notes/1109.md` (+6 -0) </details> ### 📄 Description Good catch @Jackenmen in https://github.com/actualbudget/actual/pull/948#issuecomment-1580501909 — I’ve also added a CI check to ensure bad migrations aren’t introduced in the future. I think if you have a budget that has managed to have this migration applied successfully, you’ll need to manually patch `getAppliedMigrations` in `packages/loot-core/src/server/migrate/migrations.ts` and inject a query to remove the old migration ID and insert the new one. --- <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:42:53 -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#3523
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?