Security updates: Node v20.15.1 and npm dependencies #111
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.
Description
The
alpine-node-libreoffice
image was also updated separately to enable the Node update in herehttps://apps.nrs.gov.bc.ca/int/jira/browse/SHOWCASE-3619
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist
v*.api-spec.yaml
documentation (if appropriate)Further comments
eslint
is out of date, but it was not updated as part of this PR.Linter rules are currently defined inside
package.json
- this is no longer the default behaviour as of v9.0.0 (it can be reverted by setting the environment variableESLINT_USE_FLAT_CONFIG
totrue
though) and will be removed entirely in v10.0.0.https://eslint.org/blog/2024/04/eslint-v9.0.0-released/#flat-config-is-now-the-default-and-has-some-changes