Upgrade to node 20

.github/workflows/ci.yml

@@ -11,10 +11,10 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - uses: actions/setup-node@v3
         with:
-          node-version: "18.x"
+          node-version: "20.x"
           cache: "yarn"
       - run: yarn install
       - run: npx eslint .
@@ -23,10 +23,10 @@ jobs:
     name: Prettier
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - uses: actions/setup-node@v3
         with:
-          node-version: "18.x"
+          node-version: "20.x"
           cache: "yarn"
       - run: yarn install
       - run: npx prettier --check .
@@ -35,10 +35,10 @@ jobs:
     name: Run unit tests
     runs-on: macos-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - uses: actions/setup-node@v3
         with:
-          node-version: "18.x"
+          node-version: "20.x"
           cache: "yarn"
       - run: yarn install
       - run: yarn test

.github/workflows/codeql-analysis.yml

@@ -38,7 +38,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       # Initializes the CodeQL tools for scanning.
       - name: Initialize CodeQL

CHANGELOG.md

@@ -1,3 +1,8 @@
+# Upgrade to V4.2.0
+
+The node runtime has been updated to version 20.  
+Ensure your deploy workflows use the correct node version.
+
 # Upgrade to V4
 
 The URL structure has changed to make it possible to add more options. The old URL structure is not supported anymore. But can easily be converted to the new structure.

README.md

@@ -128,7 +128,7 @@ This tests a variety of actual image conversions against problems we encountered
 
 ## Deploy Lambda function
 
-Due to internal requirements, this project has a default Serverless configuration. But you can deploy the app with your own copy op `serverless.example.yml`. We advise you to do so, because it's more flexible.
+Due to internal requirements, this project has a default Serverless configuration. But you can deploy the app with your own copy of `serverless.example.yml`. We advise you to do so, because it's more flexible.
 
 ## With your own copy of serverless.example.yml
 

package.json

@@ -4,7 +4,7 @@
   "description": "Microservice for scaling S3-stored images on the fly.",
   "main": "index.js",
   "engines": {
-    "node": "18"
+    "node": "20"
   },
   "scripts": {
     "serve": "node server/index.js",
@@ -22,7 +22,7 @@
   },
   "homepage": "https://github.com/grrr-amsterdam/s3-image-scaler#readme",
   "dependencies": {
-    "sharp": "^0.32.4"
+    "sharp": "^0.33.5"
   },
   "devDependencies": {
     "@aws-sdk/client-s3": "^3.312.0",

serverless.example.yml

@@ -29,10 +29,14 @@ provider:
               - - "arn:aws:s3:::"
                 - ${param:bucket}
                 - "/*"
-  runtime: nodejs18.x
+  runtime: nodejs20.x
   versionFunctions: false
   deploymentBucket:
     name: serverless.deployments.grrr
+  # Enable these lines when using ApiGateway:
+  # apiGateway:
+  #   binaryMediaTypes:
+  #     - "*/*"
   environment:
     BUCKET: ${param:bucket}
     IMAGE_QUALITY: ${param:image_quality}

serverless.yml

@@ -19,7 +19,7 @@ provider:
     Project: ${env:PROJECT_NAME,env:SERVICE_NAME}
   iam:
     role: ${env:SERVERLESS_ROLE}
-  runtime: nodejs18.x
+  runtime: nodejs20.x
   versionFunctions: false
   deploymentBucket:
     name: ${env:DEPLOYMENT_BUCKET}