Hi Cloud Foundry team,
I noticed that the latest version of the Node.js buildpack (v1.8.39, released on July 2, 2025) still includes Node.js 18.x.x, which officially reached its end-of-life (EOL) on April 30, 2025.
From recent activity in the repository — Issue #813 and PR #817 — I understand that the default Node.js version was updated to 22.x.x, which is great. However, the deprecated 18.x.x binary still remains part of the buildpack.
Could you please help me understand the rationale behind retaining a deprecated Node.js version in the buildpack? Is there a specific reason for not removing it entirely, or is it part of a phased transition?
This is important for us as we aim to keep our platform secure and aligned with upstream support timelines.
Thanks in advance for your insights and for all the great work you do!
Best regards,
Sujith Kizhakkekara