[GH-ISSUE #2473] Frequent breaking changes in database build & migration commands cause repeated installer and update failures #27791

Closed
opened 2026-06-10 23:15:39 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @MickLesk on GitHub (Feb 13, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2473

Describe the Bug

Over the last 2–3 weeks, Pangolin has changed its database generation and build workflow multiple times (at least 3–4 times), including renaming, removing, and reintroducing npm scripts such as:

  • build:sqlite
  • db:sqlite:generate
  • db:generate
  • db:pg:generate

These changes are not backward-compatible, often land without stable coordination, and repeatedly break fresh installs, updates, and automation scripts that rely on a predictable build and migration process.

As a result, downstream installers and update scripts are in a constant state of reactive fixes, even though no functional changes were intended on our side.

This is not an isolated incident — it is a recurring pattern tied directly to upstream changes in Pangolin’s build and database workflow.

Environment

OS Type & Version: Debian 13 (LXC)
Pangolin Version: Affected across multiple versions (1.12.x → 1.15.x)
Gerbil Version: Various
Traefik Version: 3.x
Newt Version: As bundled
Olm Version: As bundled

To Reproduce

To Reproduce

  1. Perform a fresh install or run an update using an installer that worked days earlier.

  2. Pangolin installation or update fails with one of the following patterns:

  • Missing npm scripts (Missing script: build:sqlite, Missing script: db:sqlite:generate)
  • Database generation commands renamed or removed
  • Schema or migration mismatches (SQLite errors, missing tables/columns)
  • Missing generated files in dist/ (e.g. names.json, ios_models.json)
  1. Check recent Pangolin commits or Dockerfile changes — the build/database method has changed again.

Expected Behavior

Pangolin should provide a stable, documented, and versioned database build & migration interface.

  • Breaking changes to build or DB generation commands should:

    • Be clearly documented
    • Be coordinated with a migration path
    • Not change multiple times within days
  • Installers and update scripts should not require emergency fixes every few days just to keep Pangolin operational.

  • By the way, it was never mentioned in any of the current release notes; there were always only direct commits, which makes it impossible to work with.

Originally created by @MickLesk on GitHub (Feb 13, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2473 ### Describe the Bug Over the last 2–3 weeks, Pangolin has changed its database generation and build workflow multiple times (at least 3–4 times), including renaming, removing, and reintroducing npm scripts such as: - build:sqlite - db:sqlite:generate - db:generate - db:pg:generate These changes are not backward-compatible, often land without stable coordination, and repeatedly break fresh installs, updates, and automation scripts that rely on a predictable build and migration process. As a result, downstream installers and update scripts are in a constant state of reactive fixes, even though no functional changes were intended on our side. This is not an isolated incident — it is a recurring pattern tied directly to upstream changes in Pangolin’s build and database workflow. ### Environment OS Type & Version: Debian 13 (LXC) Pangolin Version: Affected across multiple versions (1.12.x → 1.15.x) Gerbil Version: Various Traefik Version: 3.x Newt Version: As bundled Olm Version: As bundled ### To Reproduce **To Reproduce** 1. Perform a fresh install or run an update using an installer that worked days earlier. 2. Pangolin installation or update fails with one of the following patterns: - Missing npm scripts (Missing script: build:sqlite, Missing script: db:sqlite:generate) - Database generation commands renamed or removed - Schema or migration mismatches (SQLite errors, missing tables/columns) - Missing generated files in dist/ (e.g. names.json, ios_models.json) 3. Check recent Pangolin commits or Dockerfile changes — the build/database method has changed again. ### Expected Behavior Pangolin should provide a stable, documented, and versioned database build & migration interface. - Breaking changes to build or DB generation commands should: - Be clearly documented - Be coordinated with a migration path - Not change multiple times within days - Installers and update scripts should not require emergency fixes every few days just to keep Pangolin operational. - By the way, it was never mentioned in any of the current release notes; there were always only direct commits, which makes it impossible to work with.
Author
Owner

@oschwartz10612 commented on GitHub (Feb 14, 2026):

Hey, thanks for bringing this up. It is a valid complaint and we should
do better about being consistent and documenting. Right now we are
mostly officially supporting the docker container so thats why we do not
spend much time supporting native deployments but this could change.

Right now you need to set the type first and it should work like in the
Dockerfile:

 npm run set:$DATABASE && \
 npm run set:$BUILD && \
 npm run db:generate && \
 npm run build && \
 npm run build:cli

LMK if that helps

<!-- gh-comment-id:3900172361 --> @oschwartz10612 commented on GitHub (Feb 14, 2026): Hey, thanks for bringing this up. It is a valid complaint and we should do better about being consistent and documenting. Right now we are mostly officially supporting the docker container so thats why we do not spend much time supporting native deployments but this could change. Right now you need to set the type first and it should work like in the Dockerfile: npm run set:$DATABASE && \ npm run set:$BUILD && \ npm run db:generate && \ npm run build && \ npm run build:cli LMK if that helps
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#27791