Support Major Version Tags
Ricardo N Feliciano
Hey everyone. I just want to remind people that if major version alias tags exists, as the minor version alias tags exists now, these are moving tags. Moving tags will eventually point to newer images, which can contain breaking changes.
When an image updates, its not just moving from PostgreSQL v13.3 to v13.4 for example. Other tools, packages in the underlying OS, etc can also be updated at the same time. The tags for Convenience Images aren't SemVer and don't follow that policy.
Same here. We are using circle/node images as we are only interested in the latest version by major version. We cannot switch to cimg/node because of the missing major version tags in cimg/node.
Agreed that this would be quite helpful. We test open source projects like https://github.com/apollographql/apollo-server against a bunch of different major versions of Node, and it's quite convenient that
circleci/nodewe can just specify major versions. That's why we are still on
cimg/node. We know we can specify minor versions and use something like Renovate to keep them up to date but it's more work (esp since we abstract our executor away inside an orb that tags the tag as a parameter).