Refactoring

.github/dependabot.yml

@@ -5,29 +5,43 @@ updates:
     directory: "/"
     schedule:
       interval: "weekly"
-    open-pull-requests-limit: 5
+      day: "sunday"
+      time: "05:00"
+      timezone: "UTC"
+    open-pull-requests-limit: 1
     commit-message:
       prefix: "chore(deps)"
       include: "scope"
-    labels:
-      - "dependencies"
-    reviewers:
-      - "pierrevensy"
-    assignees:
-      - "pierrevensy"
+    labels: ["dependencies"]
+    reviewers: ["pierrevensy"]
+    assignees: ["pierrevensy"]
+    groups:
+      minor-updates:
+        patterns:
+          - "*"
+        update-types:
+          - "minor"
+          - "patch"
 
   # Check for updates to GitHub Actions
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
       interval: "weekly"
-    open-pull-requests-limit: 5
+      day: "sunday"
+      time: "06:00"
+      timezone: "UTC"
+    open-pull-requests-limit: 1
     commit-message:
       prefix: "chore(actions)"
       include: "scope"
-    labels:
-      - "github-actions"
-    reviewers:
-      - "pierrevensy"
-    assignees:
-      - "pierrevensy"
+    labels: ["github-actions"]
+    reviewers: ["pierrevensy"]
+    assignees: ["pierrevensy"]
+    groups:
+      minor-updates:
+        patterns:
+          - "*"
+        update-types:
+          - "minor"
+          - "patch"

.github/workflows/main.yml

@@ -15,6 +15,8 @@ jobs:
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
@@ -27,6 +29,10 @@ jobs:
         run: npm run test:cvg
       - name: Build library
         run: npm run build
+      - name: SonarQube Scan
+        uses: SonarSource/sonarqube-scan-action@v5
+        env:
+          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
 
   release-please:
     runs-on: ubuntu-latest

.github/workflows/pr.yml

@@ -4,13 +4,19 @@ on:
   pull_request:
     branches:
       - main
+    types: [opened, synchronize, reopened]
+
+permissions:
+  contents: read
 
 jobs:
   build:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
@@ -22,4 +28,9 @@ jobs:
       - name: Run tests
         run: npm run test:cvg
       - name: Build library
-        run: npm run build
+        run: npm run build
+      - name: SonarQube Scan
+        if: github.actor != 'dependabot[bot]'
+        uses: SonarSource/sonarqube-scan-action@v5
+        env:
+          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}

.github/workflows/release.yml

@@ -5,6 +5,10 @@ on:
     types:
       - published
 
+permissions:
+  contents: read
+  packages: write
+
 jobs:
   publish:
     runs-on: ubuntu-latest
@@ -27,4 +31,4 @@ jobs:
       - name: Publish to NPM
         run: npm publish --access public
         env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

CHANGELOG.md

@@ -10,4 +10,4 @@ All notable changes to the "Stone.js AWS Lambda Adapter" extension will be docum
 
 ### Features
 
-* implement aws adapters ([8695eb2](https://github.com/stonemjs/aws-lambda-adapter/commit/8695eb2c7960769d56015943ac0839e787f176d2))
+* implement aws adapters ([8695eb2](https://github.com/stone-foundation/stone-js-aws-lambda-http-adapter/commit/8695eb2c7960769d56015943ac0839e787f176d2))

CONTRIBUTING.md

@@ -46,7 +46,7 @@ The **Conventional Commits** format is structured as follows:
 ```
 
 - **`<type>`**: Specifies the type of change. Common types are `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`.
-- **`<scope>`**: (Optional) A short, descriptive word for what part of the code is affected (e.g., `auth`, `aws-lambda-adapter`).
+- **`<scope>`**: (Optional) A short, descriptive word for what part of the code is affected (e.g., `auth`, `aws-lambda-http-adapter`).
 - **`<description>`**: A brief description of the change.
 - **`Body`**: (Optional) Provides more detailed information about the commit.
 - **`Footer`**: (Optional) Used to reference issues or indicate breaking changes.
@@ -56,7 +56,7 @@ The **Conventional Commits** format is structured as follows:
 The **type** field in a Conventional Commit message is what allows you to derive the next semantic version:
 
 - **`feat`**: A new feature. Increments the **MINOR** version (e.g., `1.2.0`).
-  - Example: `feat(aws-lambda-adapter): add async pipe handling support`
+  - Example: `feat(aws-lambda-http-adapter): add async pipe handling support`
 
 - **`fix`**: A bug fix. Increments the **PATCH** version (e.g., `1.2.1`).
   - Example: `fix(api): resolve issue with null values in responses`
@@ -65,29 +65,29 @@ The **type** field in a Conventional Commit message is what allows you to derive
   - Example: `docs(readme): update installation instructions`
 
 - **`style`**: Changes related to code style (e.g., formatting, missing semicolons). No version increment.
-  - Example: `style(aws-lambda-adapter): reformat code according to ESLint rules`
+  - Example: `style(aws-lambda-http-adapter): reformat code according to ESLint rules`
 
 - **`refactor`**: A code change that does not add a feature or fix a bug. No version increment.
   - Example: `refactor(auth): simplify token validation logic`
 
 - **`test`**: Changes related to testing (e.g., adding missing tests, refactoring tests). No version increment.
-  - Example: `test(aws-lambda-adapter): add unit tests for error handling`
+  - Example: `test(aws-lambda-http-adapter): add unit tests for error handling`
 
 - **`chore`**: Maintenance tasks that do not affect the functionality of the code (e.g., updating dependencies, build-related changes). No version increment.
   - Example: `chore(deps): update lodash to version 4.17.21`
 
 - **`BREAKING CHANGE`**: Use this in the footer if the commit introduces a breaking API change, which increments the **MAJOR** version.
   - Example:
     ```
-    feat(aws-lambda-adapter): change pipe API to accept configuration object
+    feat(aws-lambda-http-adapter): change pipe API to accept configuration object
 
-    BREAKING CHANGE: The aws-lambda-adapter now requires a configuration object instead of individual parameters.
+    BREAKING CHANGE: The aws-lambda-http-adapter now requires a configuration object instead of individual parameters.
     ```
 
 ### Example Commit Messages
 1. **New Feature**:
    ```
-   feat(aws-lambda-adapter): add support for multiple output formats
+   feat(aws-lambda-http-adapter): add support for multiple output formats
    ```
    This will trigger a **MINOR** version bump.