1. Move to cflinuxfs4 (Preferred)
This is the most sustainable path. cflinuxfs4 supports the libraries required by the latest Node.js LTS releases.
- Benefit: Ensures continuous security patches, performance improvements, and compliance.
- Action: Update manifest.yml to specify stack: cflinuxfs4 and test application compatibility.
2. Pin to Older Buildpack
Applications can be "pinned" to a specific buildpack version that still contains Node.js v20.
- Risk: This leaves applications running on an unsupported runtime. No further security patches will be provided for the runtime or any other dependencies provided by the buildpack (npm, yarn, etc), increasing vulnerability to CVEs.
- Use Case: Only recommended as a short-term stopgap if immediate migration to cflinuxfs4 is technically blocked.