Skip to content
This repository was archived by the owner on Feb 26, 2025. It is now read-only.

Conversation

arosequist
Copy link
Contributor

@arosequist arosequist commented Oct 22, 2019

Node 12 went into LTS today (nodejs/node#29981) with 12.13.0. I confirmed that in Docker Hub, 12 is pointing to 12.13.0. So I think it's fine for us to include it in our options now?

In my opinion, we should consider having more specific version tags here (12.13.0 rather than just 12), but maybe that's a topic for another time, since it would require more maintenance.

{ "tag": "8", "from": "node:8" },
{ "tag": "10", "from": "node:10" }
{ "tag": "10", "from": "node:10" },
{ "tag": "12", "from": "node:12" }

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the explicit tag, could we just do a {"tag": "12.13.0", "from": "node:12.13.0"}?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that would work, I just didn't know if that was something we wanted to do. Obviously, minor/patch versions come out more frequently than major ones, so we'd have to add new ones more often in order to stay up-to-date. I don't know how annoying it would be for people if I made a new "add 12.x.y" image every time they released a new one.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we'd have to do every one, just the ones we felt were necessary. It's not like the major version ones get updated all the time anyways.

@guitarislife87 guitarislife87 self-requested a review October 31, 2019 13:31
@arosequist arosequist merged commit ecd6aac into master Oct 31, 2019
@arosequist arosequist deleted the add-node-12 branch October 31, 2019 15:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants