Skip to content

4.0: install Node 24 from NodeSource - #845

Draft
antobinary wants to merge 2 commits into
bigbluebutton:v4.0.x-releasefrom
antobinary:40-nodejs-24
Draft

4.0: install Node 24 from NodeSource#845
antobinary wants to merge 2 commits into
bigbluebutton:v4.0.x-releasefrom
antobinary:40-nodejs-24

Conversation

@antobinary

Copy link
Copy Markdown
Member

Companion to the bigbluebutton 40-nodejs-24 branch, whose debs will require nodejs (>= 24) (<< 25). Node 22 leaves maintenance 2027-04-30, during 4.0 lifetime; Node 24 is Active LTS (maintained until 2028-04-30). Must ship together with packages built against Node 24 - old debs (nodejs << 23) are not installable once this repo change is in place.

Companion to the bigbluebutton 40-nodejs-24 branch, whose debs will require
nodejs (>= 24) (<< 25). Node 22 leaves maintenance 2027-04-30, mid-4.0
lifetime; Node 24 is Active LTS (maintained until 2028-04-30). Must ship
together with packages built against Node 24 - old debs (nodejs << 23) are
not installable once this repo change is in place.
The nodesource.list setup was guarded by a file-existence check, so on an
existing server (installed with Node 22 or earlier) the block was skipped
entirely: the repo stayed on node_22.x, dist-upgrade kept nodejs at 22, and
installing the new packages that require nodejs (>= 24) failed with unmet
dependencies. Fresh installs were unaffected, which is why CI (always a
clean runner) could not catch it.

Key the guard on the repo line content instead: rewrite whenever the list
does not already point at node_$NODE_MAJOR.x (grep -qs also treats a
missing file as a mismatch). The subsequent apt-get update + dist-upgrade
then moves nodejs across the major cleanly, and the block stays idempotent
on re-runs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant