mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-25 15:01:49 +00:00
Rhys Arkins
0d5d7a8669
Refactors `getNewValue` logic to replace it with an optional `getPinnedValue()` where rangeStrategy=pin. This way each versioning module doesn't need to add and test extensive "pin" logic. This should not be breaking, but out of an abundance of caution, we'll mark it as such.
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.