0
0
Fork 0
mirror of https://github.com/renovatebot/renovate.git synced 2025-05-12 15:41:58 +00:00
renovatebot_renovate/lib/modules/versioning/lambda-node
Gareth Parker 224fa799cc
feat(versioning): Add a NodeJS Lambda Versioning module (#32480)
Co-authored-by: Rhys Arkins <rhys@arkins.net>
2025-05-06 21:51:26 +00:00
..
index.spec.ts feat(versioning): Add a NodeJS Lambda Versioning module (#32480) 2025-05-06 21:51:26 +00:00
index.ts feat(versioning): Add a NodeJS Lambda Versioning module (#32480) 2025-05-06 21:51:26 +00:00
readme.md feat(versioning): Add a NodeJS Lambda Versioning module (#32480) 2025-05-06 21:51:26 +00:00
schedule.ts feat(versioning): Add a NodeJS Lambda Versioning module (#32480) 2025-05-06 21:51:26 +00:00

Renovate's Lambda Node.js versioning is a wrapper around the existing Node.js Versioning module with the only difference being that it lists versions not currently supported by AWS as being unstable. This is intended to be a drop-in replacement for dependencies that follow the node versioning schedule if you need to keep them in line with Lambda Runtime releases.

Its primary purpose is to add Node Runtime support awareness, e.g.:

  • Old Runtimes that cannot be updated will be marked as unstable
  • Node.js LTS releases that do not have Runtimes released for them will be marked as unstable

You can not use lambda-node versioning to replace docker versioning if you are using node tags with suffixes like -alpine. This is because npm versioning treats these suffixes as implying pre-releases/instability.