Node.js 18 Docker image and CI updates #412
Merged
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.
This PR includes a bunch of commits made by a script that standardizes as much as possible our CI config across all repositories.
Along the way it also ensures we test all Node.js versions that are an LTS release, not EOL, and currently work with this repository. Any Github Actions that were out of date or used old Node.js versions (checkout and setup-node
v2
) are also updated. The geonames importer and all others will need updatedwhosonfirst
/wof-admin-lookup
deps with a new version ofbetter-sqlite3
before we can add Node.js 22 support.Also, the CI OS version is now hardcoded to ubuntu-22.04. We fooled around with an organization wide CI variable to configure that, but it broke CI in forks and doesn't really help us much, so it's now undone.
If there are any other differences in Github Actions Workflow files, they are also now removed by using a standard template.
Finally, because this repository has a Dockerfile and we just updated the Docker baseimage to support Node.js 18, there is an empty commit to trigger a new major version release.
Connects pelias/pelias#950
Connects pelias/pelias#951