Logo
Explore Help
Sign In
Mirrors/ProxMenux
1
0
Fork 0
You've already forked ProxMenux
mirror of https://github.com/MacRimi/ProxMenux.git synced 2026-06-13 11:57:09 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
d25faedc2bc690082fd708c517ee791c233692e5
ProxMenux/AppImage/ProxMenux-Monitor.AppImage.sha256

2 lines
65 B
Plaintext
Raw Normal View History

Rebuild AppImage with actual Next.js 15.1.9 + always reconcile node_modules The previous bump commit (2f24de25) shipped a binary that still carried Next.js 15.1.6 in the bundled chunks even though AppImage/package.json was at 15.1.9. Root cause: build_appimage.sh only ran `npm install` when `node_modules` did not exist; on the .50 build host node_modules had been cached since the 1.2.1 build cycle, so the bump was silently ignored and the build re-used the stale tree. Fix the script: always run `npm install --legacy-peer-deps` on every build. npm reconciles against the lockfile in under a second when everything is already in sync, so the change is free on a warm tree and correct on a stale one. Rebuild from a clean node_modules on .50, redeploy to all four hosts (SHA 4602b8d4aa130c6f...), runtime grep confirms the bundle now contains 15.1.9 with no traces of 15.1.6 left. Same architecture and threat model as before — Flask serves the static export on :8008, no Next.js runtime — but the version banner now matches the lockfile. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-06-01 22:37:44 +02:00
4602b8d4aa130c6f3cb017358d8459b473a5f05d64152fe13200b241932a73a8
Reference in New Issue Copy Permalink
Powered by Gitea Version: 1.24.5 Page: 27ms Template: 1ms
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API