[PR #7146] [MERGED] Fix docker images #48785

Closed
opened 2026-04-26 10:40:47 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/7146
Author: @MikesGlitch
Created: 3/6/2026
Status: Merged
Merged: 3/6/2026
Merged by: @MikesGlitch

Base: masterHead: fix-docker-images


📝 Commits (2)

📊 Changes

2 files changed (+9 additions, -1 deletions)

View changed files

📝 packages/sync-server/src/migrations.ts (+3 -1)
upcoming-release-notes/7146.md (+6 -0)

📄 Description

Description

Fixing migrations retrieval - it was caused by the typescript updates that have come in recently. We now need to filter out the *.d.ts files so the migration runner doesn't run them.

Docker has been failing to publish since two days ago, I think it was introduced with https://github.com/actualbudget/actual/pull/7062

As can be seen here: https://github.com/actualbudget/actual/actions/workflows/docker-edge.yml

We're getting this error when running the docker image in the pipeline & locally:

at next (/app/node_modules/migrate/lib/migrate.js:26:17)
at migrate (/app/node_modules/migrate/lib/migrate.js:76:3)
at MigrationSet.migrate (/app/node_modules/migrate/lib/set.js:123:3)
at MigrationSet.up (/app/node_modules/migrate/lib/set.js:107:8)
at file:///app/src/migrations.js:26:31
at /app/node_modules/migrate/index.js:62:5
at /app/node_modules/migrate/lib/load-migrations.js:97:7
at ReadFileContext.callback (/app/node_modules/migrate/lib/file-store.js:37:14)
at FSReqCallback.readFileAfterOpen [as oncomplete] (node:fs:297:13)

Testing

Built and ran it locally

image

Checklist

  • Release notes added (see link above)
  • No obvious regressions in affected areas
  • Self-review has been performed - I understand what each change in the code does and why it is needed

🔄 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/7146 **Author:** [@MikesGlitch](https://github.com/MikesGlitch) **Created:** 3/6/2026 **Status:** ✅ Merged **Merged:** 3/6/2026 **Merged by:** [@MikesGlitch](https://github.com/MikesGlitch) **Base:** `master` ← **Head:** `fix-docker-images` --- ### 📝 Commits (2) - [`1ecaf48`](https://github.com/actualbudget/actual/commit/1ecaf485ce188f3917a50632198cb0d922f93761) fix docker images - [`e120134`](https://github.com/actualbudget/actual/commit/e12013410116d64174afc3eae3ad8df3cbd029f3) release notes ### 📊 Changes **2 files changed** (+9 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `packages/sync-server/src/migrations.ts` (+3 -1) ➕ `upcoming-release-notes/7146.md` (+6 -0) </details> ### 📄 Description <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://github.com/actualbudget/docs#writing-good-release-notes. Try running yarn generate:release-notes *before* pushing your PR for an interactive experience. --> ## Description <!-- What does this PR do? Why is it needed? Please give context on the "why?": why do we need this change? What problem is it solving for you?--> Fixing migrations retrieval - it was caused by the typescript updates that have come in recently. We now need to filter out the `*.d.ts` files so the migration runner doesn't run them. Docker has been failing to publish since two days ago, I think it was introduced with https://github.com/actualbudget/actual/pull/7062 As can be seen here: https://github.com/actualbudget/actual/actions/workflows/docker-edge.yml ## Related issue(s) We're getting this error when running the docker image in the pipeline & locally: ``` at next (/app/node_modules/migrate/lib/migrate.js:26:17) at migrate (/app/node_modules/migrate/lib/migrate.js:76:3) at MigrationSet.migrate (/app/node_modules/migrate/lib/set.js:123:3) at MigrationSet.up (/app/node_modules/migrate/lib/set.js:107:8) at file:///app/src/migrations.js:26:31 at /app/node_modules/migrate/index.js:62:5 at /app/node_modules/migrate/lib/load-migrations.js:97:7 at ReadFileContext.callback (/app/node_modules/migrate/lib/file-store.js:37:14) at FSReqCallback.readFileAfterOpen [as oncomplete] (node:fs:297:13) ``` <!-- e.g. Fixes #123, Relates to #456 --> ## Testing Built and ran it locally <img width="675" height="410" alt="image" src="https://github.com/user-attachments/assets/3fda886b-a6ef-4e0e-928e-3a7ce695f88b" /> <!-- What did you test? How can we reproduce the issue you are fixing or how can we test the feature you built? --> ## Checklist - [x] Release notes added (see link above) - [x] No obvious regressions in affected areas - [x] Self-review has been performed - I understand what each change in the code does and why it is needed <!--- actual-bot-sections ---> --- <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-26 10:40:47 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#48785