fix: mark published AWS Lambda layers as supporting 'nodejs20.x' runt…

…ime (#4035)

Closes: #4033

.ci/Makefile

@@ -60,7 +60,7 @@ publish: validate-layer-name validate-aws-default-region
 		--layer-name "$(ELASTIC_LAYER_NAME)" \
 		--description "AWS Lambda Extension Layer for the Elastic APM Node.js Agent" \
 		--license "Apache-2.0" \
-		--compatible-runtimes nodejs18.x nodejs16.x nodejs14.x \
+		--compatible-runtimes nodejs20.x nodejs18.x nodejs16.x nodejs14.x \
 		--zip-file "fileb://./$(AWS_FOLDER)/elastic-apm-node-lambda-layer-$(GITHUB_REF_NAME).zip"
 
 # Grant public access to the given LAYER in the given AWS region

CHANGELOG.asciidoc

@@ -33,13 +33,37 @@ Notes:
 
 See the <<upgrade-to-v4>> guide.
 
+
+==== Unreleased
+
+[float]
+===== Breaking changes
+
+[float]
+===== Features
+
+[float]
+===== Bug fixes
+
+* Mark the published AWS Lambda layers as supporting the "nodejs20.x" Lambda
+  Runtime (`--compatible-runtimes`). The "nodejs20.x" runtime was released by
+  AWS on 2023-11-15. ({issues}4033[#4033])
++
+Note that this Node.js APM agent supports Node.js 20.x, so the new AWS Lambda
+runtime was supported when it was released. However, the metadata stating
+compatible runtimes (which is advisory) was not updated until now.
+
+[float]
+===== Chores
+
+
 [[release-notes-4.5.4]]
 ==== 4.5.4 - 2024/05/13
 
 [float]
 ===== Bug fixes
 
-- Change how the "cookie" HTTP request header is represented in APM transaction
+* Change how the "cookie" HTTP request header is represented in APM transaction
   data to avoid a rare, but possible, intake bug where the transaction could be
   rejected due to a mapping conflict.
 +