I am currently on 12.83.0 and the upgrade fails with the output below.
root@vultr:~/misskey# NODE_ENV=production yarn build
yarn run v1.22.5
$ npm run build-webpack && npm run build-ts && npm run build-gulp
npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1627044116136-0.5387218473502009/node but npm is using /usr/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
> firstname.lastname@example.org build-webpack /home/misskey/misskey
92% sealing asset processing TerserPlugin
<--- Last few GCs --->
[17015:0x4b6af50] 292263 ms: Mark-sweep (reduce) 972.4 (1000.4) -> 971.6 (1001.6) MB, 3948.8 / 0.0 ms (average mu = 0.121, current mu = 0.013) allocation failure scavenge might not succeed
[17015:0x4b6af50] 295549 ms: Mark-sweep (reduce) 972.7 (1000.6) -> 971.8 (1001.9) MB, 3272.5 / 0.0 ms (average mu = 0.069, current mu = 0.004) allocation failure scavenge might not succeed
<--- JS stacktrace --->
1: 0xa04200 node::Abort() [webpack]
2: 0x94e4e9 node::FatalError(char const*, char const*) [webpack]
3: 0xb7978e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [webpack]
4: 0xb79b07 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [webpack]
5: 0xd34395 [webpack]
6: 0xd34f1f [webpack]
7: 0xd42fab v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack]
8: 0xd46b6c v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
9: 0xd1524b v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [webpack]
10: 0x105b23f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [webpack] 11: 0x1401219 [webpack]
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! email@example.com build-webpack: `webpack`
npm ERR! Exit status 134
npm ERR! Failed at the firstname.lastname@example.org build-webpack script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/misskey/.npm/_logs/2021-07-23T12_46_55_283Z-debug.log
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.