How can I upgrade from 4.5.1 to 4.5.2?
-
I tried the recommended method which is upgrading using the command ```
./nodebb upgradeStill, it can't be updated. I guess I'll have to use the "Git fetch", but the tutorial over here (https://docs.nodebb.org/configuring/upgrade/) can't help me at all so I wonder what I need to do, I'm using a Debian 12 system...
-
I tried the recommended method which is upgrading using the command ```
./nodebb upgradeStill, it can't be updated. I guess I'll have to use the "Git fetch", but the tutorial over here (https://docs.nodebb.org/configuring/upgrade/) can't help me at all so I wonder what I need to do, I'm using a Debian 12 system...
Shaknunic you have to use
git pullto get the latest code (orgit checkout v4.5.2or whatever version).If you're not using git then you'll have to download the files and replace the existing folder with the new files. Let me know if you need help with that.
-
I ended up making a backup from the database and re-setup everything since it didn't work replacing everything for the new files as I was already assume it would happen, I'm having an error message about theme
DEPRECATION WARNING [mixed-decls]: Sass's behavior for declarations that appear after nested rules will be changing to match the behavior specified by CSS in an upcoming version. To keep the existing behavior, move the declaration above the nested rule. To opt into the new behavior, wrap the declaration in `& {}`. More info: https://sass-lang.com/d/mixed-decls ┌──> ../../../nodebb-theme-harmony/scss/modules/cover.scss 23 │ pointer-events: none; │ ^^^^^^^^^^^^^^^^^^^^ declaration ╵ ┌──> ../../../bootstrap/scss/mixins/_transition.scss 21 │ ┌ @media (prefers-reduced-motion: reduce) { 22 │ │ transition: none; 23 │ │ } │ └─── nested rule ╵ ../../../nodebb-theme-harmony/scss/modules/cover.scss 23:3 @import ../../../nodebb-theme-harmony/scss/harmony.scss 21:9 @import theme.scss 1:9 @import - 56:9 root stylesheetJust not quite sure what I'm suppose to change... the CSS code apparently changed and the theme unfortunate didn't get the update for it...
-
I ended up making a backup from the database and re-setup everything since it didn't work replacing everything for the new files as I was already assume it would happen, I'm having an error message about theme
DEPRECATION WARNING [mixed-decls]: Sass's behavior for declarations that appear after nested rules will be changing to match the behavior specified by CSS in an upcoming version. To keep the existing behavior, move the declaration above the nested rule. To opt into the new behavior, wrap the declaration in `& {}`. More info: https://sass-lang.com/d/mixed-decls ┌──> ../../../nodebb-theme-harmony/scss/modules/cover.scss 23 │ pointer-events: none; │ ^^^^^^^^^^^^^^^^^^^^ declaration ╵ ┌──> ../../../bootstrap/scss/mixins/_transition.scss 21 │ ┌ @media (prefers-reduced-motion: reduce) { 22 │ │ transition: none; 23 │ │ } │ └─── nested rule ╵ ../../../nodebb-theme-harmony/scss/modules/cover.scss 23:3 @import ../../../nodebb-theme-harmony/scss/harmony.scss 21:9 @import theme.scss 1:9 @import - 56:9 root stylesheetJust not quite sure what I'm suppose to change... the CSS code apparently changed and the theme unfortunate didn't get the update for it...
Shaknunic I think that might be okay as that is just a warning.
-
I get the below error on upgrade from 4.5.1 to 4.5.2
2025-09-30T12:40:45.076Z [6000/4185747] - info: Initializing NodeBB v4.5.2 https://watchtower.phenomlab.com failed to asynchronously prepare wasm: CompileError: WebAssembly.instantiate(): section (code 1, "Type") extends past end of the module (length 7299055, remaining bytes 81343) @+8 Aborted(CompileError: WebAssembly.instantiate(): section (code 1, "Type") extends past end of the module (length 7299055, remaining bytes 81343) @+8) 2025-09-30T12:40:45.835Z [6000/4185747] - error: uncaughtException: Aborted(CompileError: WebAssembly.instantiate(): section (code 1, "Type") extends past end of the module (length 7299055, remaining bytes 81343) @+8). Build with -sASSERTIONS for more info. RuntimeError: Aborted(CompileError: WebAssembly.instantiate(): section (code 1, "Type") extends past end of the module (length 7299055, remaining bytes 81343) @+8). Build with -sASSERTIONS for more info. at Z (/home/phenomlab/domains/watchtower.phenomlab.com/nodebb/node_modules/satori/dist/index.cjs:2:23827) at /home/phenomlab/domains/watchtower.phenomlab.com/nodebb/node_modules/satori/dist/index.cjs:3:20524 {"date":"Tue Sep 30 2025 13:40:45 GMT+0100 (British Summer Time)","error":{},"exception":true,"os":{"loadavg":[0.71,0.24,0.14],"uptime":1163433.07},"process":{"argv":["/usr/bin/node","/home/phenomlab/domains/watchtower.phenomlab.com/nodebb/app.js"],"cwd":"/home/phenomlab/domains/watchtower.phenomlab.com/nodebb","execPath":"/usr/bin/node","gid":1009,"memoryUsage":{"arrayBuffers":20412565,"external":24833467,"heapTotal":96968704,"heapUsed":64413424,"rss":178364416},"pid":4185747,"uid":1015,"version":"v20.19.5"},"stack":"RuntimeError: Aborted(CompileError: WebAssembly.instantiate(): section (code 1, \"Type\") extends past end of the module (length 7299055, remaining bytes 81343) @+8). Build with -sASSERTIONS for more info.\n at Z (/home/phenomlab/domains/watchtower.phenomlab.com/nodebb/node_modules/satori/dist/index.cjs:2:23827)\n at /home/phenomlab/domains/watchtower.phenomlab.com/nodebb/node_modules/satori/dist/index.cjs:3:20524","trace":[{"column":23827,"file":"/home/phenomlab/domains/watchtower.phenomlab.com/nodebb/node_modules/satori/dist/index.cjs","function":"Z","line":2,"method":null,"native":false},{"column":20524,"file":"/home/phenomlab/domains/watchtower.phenomlab.com/nodebb/node_modules/satori/dist/index.cjs","function":null,"line":3,"method":null,"native":false}]}EDIT: fixed using
cd /path/to/nodebb rm -rf node_modules build npm install --production ./nodebb build -
julian If it was showing up once it will be fine, but the issue is that message shows up every second which can easily overload the RAM with so many warnings then would be an issue... I guess I'll have to be using 4.5.1 until the issue with the theme is fixed... The software itself works, but that warning message is a bit concerning.
-
julian If it was showing up once it will be fine, but the issue is that message shows up every second which can easily overload the RAM with so many warnings then would be an issue... I guess I'll have to be using 4.5.1 until the issue with the theme is fixed... The software itself works, but that warning message is a bit concerning.
Shaknunic the errors show up for awhile and then they stop. It's a noisy warning from the SCSS people and we can't fix it until Bootstrap fixes it (I think)