Frequent breaking changes in database build & migration commands cause repeated installer and update failures #246

New Issue

MrUnknownDE · 2026-04-05T17:03:26+02:00

MrUnknownDE commented

2026-04-05 17:03:26 +02:00

Originally created by @MickLesk on 2/13/2026

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

Perform a fresh install or run an update using an installer that worked days earlier.
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)

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 2/13/2026* ### 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.

MrUnknownDE closed this issue

2026-04-05 17:03:26 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#246