-
-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Clear and concise description of the problem
knowing node has a version utility library, it's possible to make the node version upgrade completely hands-free or human-labor-free,
Suggested solution
Same method as official docs method using @nodevu/core.
Make sure to check available "node alpine" tags in Docker Hub, preferably using Docker CLI. Especially the Alpine Docker image version, otherwise, it is possible to break the build when the Alpine version is not available.
It's simple, we delete EoL versions and we create a new version by copying existing files and folders, but updating the folder name and replacing some strings.
Reference:
- https://nodejs.org/en/about/previous-releases
- https://github.com/nodejs/nodejs.org/blob/main/apps/site/pages/en/about/previous-releases.mdx?plain=1
- https://github.com/nodejs/nodejs.org/blob/0a6bec296abbc82c82559b0d4c99123bfadfd8e0/apps/site/components/Releases/PreviousReleasesTable/index.tsx#L8
- https://github.com/nodejs/nodejs.org/blob/0a6bec296abbc82c82559b0d4c99123bfadfd8e0/apps/site/next-data/generators/releaseData.mjs#L6
Alternative
Alternatively, we can use our own solution by reading docker-node repo page.
Use curl and jq to fetch the repo page and determine which major version exists; we will then auto-update our repo docs accordingly. Using this method, make sure to check that the available "node alpine", especially the alpine version number, exists in the Docker Hub. So, we need to use the Docker CLI to get that information or read it directly from Docker Hub's web interface.
It's simple, we delete EoL versions and we create a new version by copying existing files and folders, but updating the folder name and replacing some strings.
Reference: -
Additional context
We prefer to use the newest Alpine version available, since we want our Docker image future proof and we build it daily.
But other opinions are welcome. We love feedback.
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.