Test version bump

CHANGELOG.md

@@ -1,3 +1,7 @@
+## [2.12.0] - 2024-02-01
+
+- testing
+
 ## [2.11.0] - 2021-01-25
 
 - Fix local development
@@ -31,7 +35,6 @@
 
 - `PUBLIC_WT_URL` generation fixed for specific clusters
 
-
 ## [2.6.2] - 2019-03-28
 
 - Clarify authorization information and claims
@@ -45,19 +48,19 @@
 **BREAKING CHANGE:** After upgrading to 2.6 or a higher version, you need to do the following to continue operation:
 
 1. Rotate your key and re-publish the rule on the extension's Configuration page. This is needed due to the changed
- logic on storing and handling the Api Key.
+   logic on storing and handling the Api Key.
 2. The rule published by this extension is named `auth0-authorization-extension`. Check your tenant's rules. If you see
- a rule named `auth0-authz` disable/remove it **by following the instructions below**.
+   a rule named `auth0-authz` disable/remove it **by following the instructions below**.
 
- #### Checklist to disable/remove `auth0-authz` rule:
+#### Checklist to disable/remove `auth0-authz` rule:
 
- 1. Go to your tenant's rules
- 2. Modify `auth0-authorization-extension`'s order to be right next to `auth0-authz` extension.
- 3. Check `auth0-authz` to be sure that it is not authored by you and no manual changes are done.
- 4. Check `auth0-authz` to be sure that disabling/removing it will not change authorization flow in a way to grant
-  access or privileges to users that shouldn't have it.
- 5. Disable the `auth0-authz` rule. After verifying that everything is in order, you can choose to keep
-  it disabled or remove it.
+1.  Go to your tenant's rules
+2.  Modify `auth0-authorization-extension`'s order to be right next to `auth0-authz` extension.
+3.  Check `auth0-authz` to be sure that it is not authored by you and no manual changes are done.
+4.  Check `auth0-authz` to be sure that disabling/removing it will not change authorization flow in a way to grant
+    access or privileges to users that shouldn't have it.
+5.  Disable the `auth0-authz` rule. After verifying that everything is in order, you can choose to keep
+    it disabled or remove it.
 
 Failing to do these will cause an "InvalidApiKey" or "You are not allowed to access this application." error on rule
 execution.
@@ -87,6 +90,7 @@ execution.
 - Optimizations to avoid Blocking event loop
 
 ## [2.4.8] - 2017-12-14
+
 - Uses `setImmediate` to avoid blocks
 
 ## [2.4.7] - 2017-11-28

package.json

@@ -1,6 +1,6 @@
 {
   "name": "auth0-authz-extension",
-  "version": "2.11.0",
+  "version": "2.12.0",
   "description": "Auth0 Authorization Extension",
   "engines": {
     "node": ">=12"
@@ -219,4 +219,4 @@
     "webpack-stats-plugin": "0.1.5",
     "webtask-bundle": "3.0.1"
   }
-}
+}

webtask.json

@@ -1,7 +1,7 @@
 {
   "title": "Auth0 Authorization",
   "name": "auth0-authz",
-  "version": "2.11.0",
+  "version": "2.12.0",
   "author": "auth0",
   "description": "This extension gives Auth0 customers the possibility to manage group memberships for their users.",
   "type": "application",