Fix type bug in cors

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,14 +7,14 @@ assignees: ''
 
 ---
 
-**Describe the bug**
+## Describe the bug
 A clear and concise description of what the bug is.
 
-**To Reproduce**
+## To Reproduce
 The following minimal code reproduces the error:
 
-**Expected behavior**
+## Expected behavior
 A clear and concise description of what you expected to happen.
 
-**Additional context**
+## Additional context
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -11,15 +11,15 @@ assignees: ''
 A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
 
 ** Would you be willing to help with a PR? **
-[ ] Yes, absolutely
-[ ] Yes, with some guidance
-[ ] Unfortunately no time :'-(
+- [ ] Yes, absolutely
+- [ ] Yes, with some guidance
+- [ ] Unfortunately no time :'-(
 
-**Describe the solution you'd like**
+## Describe the solution you'd like
 A clear and concise description of what you want to happen.
 
-**Describe alternatives you've considered**
+## Describe alternatives you've considered
 A clear and concise description of any alternative solutions or features you've considered.
 
-**Additional context**
+## Additional context
 Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,10 @@
+<!-- Please only open PRs for issues in place. If there is no issue, please open the issue first. Then create this PR and link it to the issue by adding the issue number in the line below. -->
+Closes #<!-- Replace this comment with the issue number -->
+
+## Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] I have updated the documentation accordingly.
+- [ ] I have read the **CONTRIBUTING** document.
+
+<!-- If you wrote meaningful commit messages, this is it. If you don't feel confident that your commit messages fully explain your changes and your reasoning behind it, then you can add more information to this PR. Or, even better, update your commit messages ;) -->

dependabot.yml → .github/dependabot.yml

@@ -1,6 +1,6 @@
 version: 2
 updates:
   - package-ecosystem: "npm"
-    directory: "/packages"
+    directory: "/"
     schedule:
-      interval: "weekly"
+      interval: "daily"

.github/issue_label_bot.yaml

@@ -0,0 +1,4 @@
+label-alias:
+  bug: 'bug'
+  feature_request: 'enhancement'
+  question: 'question'

.github/labels.yml

@@ -0,0 +1,36 @@
+- name: "bug"
+  color: "d73a4a"
+  description: "Something isn't working"
+- name: "documentation"
+  color: "0075ca"
+  description: "Improvements or additions to documentation"
+- name: "duplicate"
+  color: "cfd3d7"
+  description: "This issue or pull request already exists"
+- name: "enhancement"
+  color: "a2eeef"
+  description: "New feature or request"
+- name: "chore"
+  color: "CD026F"
+  description: "Changes to how we maintain the repository"
+- name: "good first issue"
+  color: "7057ff"
+  description: "Good for newcomers"
+- name: "help wanted"
+  color: "008672"
+  description: "This issue is ready for contributing a PR"
+- name: "question"
+  color: "d876e3"
+  description: "Further information is requested"
+- name: "wontfix"
+  color: "ffffff"
+  description: "This will not be worked on"
+- name: "stale"
+  color: "4252e5"
+  description: "Stale issues and PRs will be closed automatically"
+- name: "hacktoberfest"
+  color: "FF8AE2"
+  description: "Issues prepared for Hacktoberfest"
+- name: "invalid"
+  color: "FCBA03"
+  description: "PRs marked as invalid so they don't count for Hacktoberfest"

.github/mergify.yml

@@ -0,0 +1,27 @@
+pull_request_rules:
+  - name: merge reviewed and built PRs
+    conditions:
+      - base=main
+      - "#approved-reviews-by>=1"
+      - status-success=build
+      - status-success=license/cla
+    actions:
+      merge:
+        method: merge
+
+  - name: merge reviewed PRs from the repo owner
+    conditions:
+      - author=dbartholomae
+      - base=main
+      - status-success=build
+    actions:
+      merge:
+        method: merge
+
+  - name: automatic merge for Dependabot pull requests
+    conditions:
+      - author~=^dependabot(|-preview)\[bot\]$
+      - status-success=build
+    actions:
+      merge:
+        method: merge

.github/workflows/close-stale-issues.yml

@@ -0,0 +1,18 @@
+name: "Close stale issues"
+on:
+  schedule:
+    - cron: "0 0 * * *"
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v3
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          days-before-stale: 60
+          days-before-close: 7
+          stale-issue-message: This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
+          stale-pr-message: This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
+          stale-issue-label: stale
+          stale-pr-label: stale

.github/workflows/update-labels.yml

@@ -0,0 +1,24 @@
+name: Sync labels
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - .github/labels.yml
+      - .github/workflows/update-labels.yml
+
+jobs:
+  labeler:
+    runs-on: ubuntu-latest
+    steps:
+      -
+        name: Checkout
+        uses: actions/checkout@v2
+      -
+        name: Run Labeler
+        if: success()
+        uses: crazy-max/ghaction-github-labeler@v3
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          yaml-file: .github/labels.yml

SECURITY.md

@@ -0,0 +1,17 @@
+# Security policy
+
+If you find a security vulnerability, do NOT open an issue. Email
+[[email protected]](mailto:[email protected]&subject=Security%20vulnerability%20in%20repo)
+instead. This reduces the risk of criminals getting aware and exploiting the
+vulnerability before we got a chance to fix it.
+
+In order to determine whether you are dealing with a security issue, ask yourself these two questions:
+* Can I access something that's not mine, or something I shouldn't have access to?
+* Can I disable something for other people?
+
+If the answer to either of those two questions are "yes", then you're probably dealing with a security issue.
+Note that even if you answer "no" to both questions, you may still be dealing with a security issue, so if you're
+unsure, just email us at [[email protected]](mailto:[email protected]&subject=Security%20vulnerability%20in%20repo).
+
+If the bug is not security related, please use the corresponding issue template
+to submit it on GitHub.

SUPPORT.md

@@ -0,0 +1,3 @@
+At the moment, it is totally fine to open an issue if you have any questions.
+This might change though depending on the time needed to answer.
+Also, please note that this is free and open source software and there is no guarantees on any kind of support from our side.

_templates/middleware/new/package/package.json.t

@@ -69,7 +69,7 @@ to: packages/<%= h.inflection.dasherize(name.toLowerCase()) %>/package.json
     "supertest": "^4.0.2",
     "ts-jest": "^25.3.1",
     "ts-loader": "^6.2.2",
-    "typescript": "^3.7.5",
+    "typescript": "^4.1.0",
     "wait-on": "^5.2.0",
     "webpack": "^4.41.5"
   },

common/changes/@lambda-middleware/class-validator/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/class-validator",
+      "comment": "ast",
+      "type": "major"
+    }
+  ],
+  "packageName": "@lambda-middleware/class-validator",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/compose/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/compose",
+      "comment": "ast",
+      "type": "minor"
+    }
+  ],
+  "packageName": "@lambda-middleware/compose",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/cors/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/cors",
+      "comment": "Before, cors middleware could be used for handler of all kinds of events. Now it can only be used for APIGatewayEvents. This should not cause much trouble, as the middleware already returned APIGatewayResponses only.",
+      "type": "major"
+    }
+  ],
+  "packageName": "@lambda-middleware/cors",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/do-not-wait/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/do-not-wait",
+      "comment": "Update TypeScript version",
+      "type": "patch"
+    }
+  ],
+  "packageName": "@lambda-middleware/do-not-wait",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/http-error-handler/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/http-error-handler",
+      "comment": "Before, ErrorHandler middleware could be used for handler of all kinds of events. Now it can only be used for APIGatewayEvents. This should not cause much trouble, as the middleware already returned APIGatewayResponses only.",
+      "type": "major"
+    }
+  ],
+  "packageName": "@lambda-middleware/http-error-handler",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/http-header-normalizer/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/http-header-normalizer",
+      "comment": "Update TypeScript version",
+      "type": "patch"
+    }
+  ],
+  "packageName": "@lambda-middleware/http-header-normalizer",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/ie-no-open/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/ie-no-open",
+      "comment": "Update TypeScript version",
+      "type": "patch"
+    }
+  ],
+  "packageName": "@lambda-middleware/ie-no-open",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/json-serializer/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/json-serializer",
+      "comment": "Before, JsonSerializer middleware could be used for handler of all kinds of events. Now it can only be used for APIGatewayEvents. This should not cause much trouble, as the middleware already returned APIGatewayResponses only.",
+      "type": "major"
+    }
+  ],
+  "packageName": "@lambda-middleware/json-serializer",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/jwt-auth/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/jwt-auth",
+      "comment": "Require node types",
+      "type": "patch"
+    }
+  ],
+  "packageName": "@lambda-middleware/jwt-auth",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/middy-adaptor/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/middy-adaptor",
+      "comment": "Update TypeScript version",
+      "type": "patch"
+    }
+  ],
+  "packageName": "@lambda-middleware/middy-adaptor",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/no-sniff/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/no-sniff",
+      "comment": "Update TypeScript version",
+      "type": "patch"
+    }
+  ],
+  "packageName": "@lambda-middleware/no-sniff",
+  "email": "[email protected]"
+}

common/changes/@lambda-middleware/utils/fix_type_bug_in_cors_2020-10-23-14-18.json

@@ -0,0 +1,11 @@
+{
+  "changes": [
+    {
+      "packageName": "@lambda-middleware/utils",
+      "comment": "Update TypeScript version",
+      "type": "patch"
+    }
+  ],
+  "packageName": "@lambda-middleware/utils",
+  "email": "[email protected]"
+}