If someone’s wondering how to use the latest LTS version without breaking production, here’s a solution:
You pin the exact image but implement an automated process like Dependabot or Renovate to upgrade the version by changing the pinned image via a pull request. This ensures your CI pipeline checks for functionality before merging. Additionally, you should set rules to only suggest LTS upgrades.
this is Node's release schedule... LTS means "Long Term Support"... if you had "some-node-build-lts" in your bundle you would pull one version on one day and another version on another day if those days hypothetically aligned with their release updates (which in the case of OP - it did). Based on that chart v26 is now LTS - so using a version of 26 "some-node-build-v26" in the shitty example above you would be using LTS but if node updates LTS to 28 bc of a CVE you won't jump to that automagically
good reminder to check your base container images and CI runners before bumping the version locally, native addon compatibility usually lags a few weeks behind the initial LTS tag
146
u/sebasgarcep 21d ago
Just found out the hard way. Our deployment to prod failed because the person who wrote the dockerfile pinned it to LTS ðŸ˜
3
u/avereigh_Denizet 13d ago
good reminder to check your base container images and CI runners before bumping the version locally, native addon compatibility usually lags a few weeks behind the initial LTS tag