In cases where we are using specific patch level node versions we should switch those to major only.
So for instance 18.19.1, should become 18, or more specifically, where we currently build just a terascope/node-base:18.19.1 image, instead, we would build a terascope/node-base:18.19.1 image, and add the tags terascope/node-base:18.19 and terascope/node-base:18.
Then we change our downstream processes to use the terascope/node-base:18 image. But we ALWAYs tag all three. This means that terascope/node-base:18 gets over written all of the time, but IF theres problem with a minor or patch level build, we can change our downstream projects to temporarily use the most recent version without the issue.
In cases where we are using specific patch level node versions we should switch those to major only.
So for instance 18.19.1, should become 18, or more specifically, where we currently build just a
terascope/node-base:18.19.1
image, instead, we would build aterascope/node-base:18.19.1
image, and add the tagsterascope/node-base:18.19
andterascope/node-base:18
.Then we change our downstream processes to use the
terascope/node-base:18
image. But we ALWAYs tag all three. This means thatterascope/node-base:18
gets over written all of the time, but IF theres problem with a minor or patch level build, we can change our downstream projects to temporarily use the most recent version without the issue.