chore(parser): add parser to release steps

.github/actions/cached-node-modules/action.yml

@@ -34,17 +34,18 @@ runs:
     - name: Build packages
       # Regardless of whether the cache was hit or not, we need to build the packages, unless the caller says otherwise
       if: inputs.build == 'true'
-      # We build the shared package first, then the others in parallel to speed up the process
+      # We build the commons and jmspath packages first, then the others in parallel to speed up the process
       # even though we could just run `npm run build` in the root folder and build them in
       # sequence, but still in the correct order.
       run: |
-        npm run build -w packages/commons
+        npm run build -w packages/commons 
         npm run build -w packages/jmespath
         npm run build -w packages/logger & \
         npm run build -w packages/tracer & \
         npm run build -w packages/metrics & \
         npm run build -w packages/parameters & \
         npm run build -w packages/idempotency & \
         npm run build -w packages/batch & \
-        npm run build -w packages/testing 
+        npm run build -w packages/testing & \
+        npm run build -w packages/parser
       shell: bash

.github/scripts/release_patch_package_json.js

@@ -18,7 +18,7 @@ if (process.argv.length < 3) {
 const basePath = resolve(process.argv[2]);
 const packageJsonPath = join(basePath, 'package.json');
 const alphaPackages = [];
-const betaPackages = [];
+const betaPackages = ['@aws-lambda-powertools/parser'];
 
 (() => {
   try {

.github/workflows/reusable-run-linting-check-and-unit-tests.yml

@@ -28,9 +28,9 @@ jobs:
         with:
           nodeVersion: ${{ matrix.version }}
       - name: Run linting
-        run: npm run lint -w packages/commons -w packages/logger -w packages/tracer -w packages/metrics -w packages/parameters -w packages/idempotency -w packages/batch -w packages/jmespath
+        run: npm run lint -w packages/commons -w packages/logger -w packages/tracer -w packages/metrics -w packages/parameters -w packages/idempotency -w packages/batch -w packages/jmespath -w packages/parser
       - name: Run unit tests
-        run: npm t -w packages/commons -w packages/logger -w packages/tracer -w packages/metrics -w packages/parameters -w packages/idempotency -w packages/batch -w packages/jmespath
+        run: npm t -w packages/commons -w packages/logger -w packages/tracer -w packages/metrics -w packages/parameters -w packages/idempotency -w packages/batch -w packages/jmespath -w packages/parser
   check-examples:
     runs-on: ubuntu-latest
     env:

lerna.json

@@ -9,6 +9,7 @@
     "packages/batch",
     "packages/testing",
     "packages/jmespath",
+    "packages/parser",
     "examples/app",
     "layers",
     "docs/snippets"

packages/parser/README.md

@@ -1,5 +1,12 @@
 # Powertools for AWS Lambda (TypeScript) - Parser Utility <!-- omit in toc -->
 
+
+| ⚠️ **WARNING: Do not use this utility in production just yet!** ⚠️                                                                                                                                                                                                                                                                                                  |
+| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| This AWS Lambda Powertools for TypeScript utility is currently released as beta developer preview and is intended strictly for feedback and testing purposes only.  <br/>This version is not stable, and significant breaking changes might incur before going [before the GA release](https://github.com/aws-powertools/powertools-lambda-typescript/milestone/16). | _ |
+
+
+
 Powertools for AWS Lambda (TypeScript) is a developer toolkit to implement Serverless [best practices and increase developer velocity](https://docs.powertools.aws.dev/lambda/typescript/latest/#features).
 
 You can use the package in both TypeScript and JavaScript code bases.

packages/parser/package.json

@@ -7,7 +7,7 @@
     "url": "https://aws.amazon.com"
   },
   "publishConfig": {
-    "access": "restricted"
+    "access": "public"
   },
   "scripts": {
     "test": "npm run test:unit",
@@ -91,9 +91,16 @@
     "aws",
     "lambda",
     "powertools",
-    "batch",
-    "batch-processing",
+    "parser",
+    "zod",
+    "parse",
+    "events",
+    "payloads",
+    "inputs",
+    "validate",
+    "validation",
     "serverless",
+    "typescript",
     "nodejs"
   ],
   "peerDependencies": {