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

[PR #4343] [MERGED] rename two migrations to realign with convention #5328

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

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/4343
Author: @matt-fidd
Created: 2/9/2025
Status: ✅ Merged
Merged: 2/16/2025
Merged by: @matt-fidd

Base: master ← Head: migrations-rename

📝 Commits (3)

📊 Changes

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

View changed files

📝 packages/loot-core/migrations/1736640000000_custom_report_sorting.sql (+0 -0)
📝 packages/loot-core/migrations/1738491452000_sorting_rename.sql (+0 -0)
➕ upcoming-release-notes/4343.md (+6 -0)

📄 Description

I made a mistake in #4141 and added a double underscore to the migration, this was copied in #4276.

This change only renames these, which does not cause a problem as the timestamp is used under the hood to track them.

The migrations check workflow is expected to fail because these are dated the same as two existing and before the most recent

To test, upload a file from v25.2.1 or later (edge) and see that it doesn't break.

🔄 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/4343 **Author:** [@matt-fidd](https://github.com/matt-fidd) **Created:** 2/9/2025 **Status:** ✅ Merged **Merged:** 2/16/2025 **Merged by:** [@matt-fidd](https://github.com/matt-fidd) **Base:** `master` ← **Head:** `migrations-rename` --- ### 📝 Commits (3) - [`eb6930b`](https://github.com/actualbudget/actual/commit/eb6930bb7d12b77bc9d1c689a0b8e435de370f82) rename migrations - [`3c0d2bc`](https://github.com/actualbudget/actual/commit/3c0d2bc87af9b22f85d0eb5a43241bf0ea14968a) note - [`4342841`](https://github.com/actualbudget/actual/commit/4342841b7bb60d81db9265f3cc3b5f3e7b510f11) Merge branch 'master' into migrations-rename ### 📊 Changes **3 files changed** (+6 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/loot-core/migrations/1736640000000_custom_report_sorting.sql` (+0 -0) 📝 `packages/loot-core/migrations/1738491452000_sorting_rename.sql` (+0 -0) ➕ `upcoming-release-notes/4343.md` (+6 -0) </details> ### 📄 Description I made a mistake in #4141 and added a double underscore to the migration, this was copied in #4276. This change only renames these, which does not cause a problem as the timestamp is used under the hood to track them. The migrations check workflow is expected to fail because these are dated the same as two existing and before the most recent To test, upload a file from v25.2.1 or later (edge) and see that it doesn't break. --- <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:10:39 -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#5328
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?