mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-07 21:30:36 -05:00
[GH-ISSUE #2929] Upgrade from 1.17.0 to 1.18.0 fails #9035
Reference in New Issue
Block a user
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?
Originally created by @coro1404 on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2929
Originally assigned to: @oschwartz10612 on GitHub.
Describe the Bug
pangolin |
pangolin | > @fosrl/pangolin@0.0.0 start
pangolin | > ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs
pangolin |
pangolin | Starting migrations from version 1.17.0
pangolin | Migrations to run: 1.18.0
pangolin | Running migration 1.18.0
pangolin | Running setup script 1.18.0...
pangolin | Found 5 existing targetHealthCheck row(s) to migrate
pangolin | Found 1 existing siteResource(s) to migrate to networks
pangolin | Failed to migrate db: SqliteError: NOT NULL constraint failed: __new_siteResources.tcpPortRangeString
pangolin | at file:///app/dist/migrations.mjs:5029:9
pangolin | at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24)
pangolin | at Object.migration33 [as run] (file:///app/dist/migrations.mjs:5111:7)
pangolin | at executeScripts (file:///app/dist/migrations.mjs:5378:27)
pangolin | at async runMigrations (file:///app/dist/migrations.mjs:5335:7)
pangolin | at async run (file:///app/dist/migrations.mjs:5308:3)
pangolin | at async file:///app/dist/migrations.mjs:5306:1 {
pangolin | code: 'SQLITE_CONSTRAINT_NOTNULL'
pangolin | }
Environment
To Reproduce
Switch to 1.18. in docker compose
Expected Behavior
Upgrade works seamless
@maddler commented on GitHub (Apr 29, 2026):
Similar issue here
@oschwartz10612 commented on GitHub (Apr 29, 2026):
This will be fixed in the 1.18.1 release which will happen in an hour or two
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Should be fixed with the 1.18.1 update just released. LMK
@maddler commented on GitHub (Apr 29, 2026):
Giving a go now. Installed fine. Checking everything now.