Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New stable release Debian 10 "buster" was released 2019-07-06. Add new "buster" and "buster-slim" image variants for all currently supported Node.js versions (v8, v10, v12).
This is basically #1055 redone without unrelated changes. The buster image variants use same Yarn as current stretch images are using.
This does not change the default variant. However I'd like to repeat part of what I commented in #1055.
Node.js v12.x LTS ends 2022-04-01, which is later than Debian 9 stretch ordinary security support (one year from the release of Debian 10 buster), but no later than Debian 9 stretch LTS support (June 2022).
However in my opinion preferred solution is to switch
node:12
andnode:12-slim
images to use Debian 10 buster before Node.js v12.x enters active LTS period on 2019-10-22. In any case it would be useful to write down the principles how the operating system version are selected and updated just like CONTRIBUTING.md describes update cycle for Node.js, NPM and Yarn. Changing Debian version during Node.js LTS period causes breakages such as explained in #937.