From 5b50cd25f3a1c48b09f4dd5ca6869b17f178276d Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Mon, 17 Feb 2025 22:22:24 +0000
Subject: [PATCH] Release new version

---
 .changeset/tiny-years-bake.md | 27 ---------------------------
 CHANGELOG.md                  | 28 ++++++++++++++++++++++++++++
 package.json                  |  2 +-
 3 files changed, 29 insertions(+), 28 deletions(-)
 delete mode 100644 .changeset/tiny-years-bake.md

diff --git a/.changeset/tiny-years-bake.md b/.changeset/tiny-years-bake.md
deleted file mode 100644
index be01f90b..00000000
--- a/.changeset/tiny-years-bake.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-'@evervault/sdk': minor
----
-
-Extend Relay outbound/forward proxy support in Node to include the ability to filter requests by path using `decryptionDomains`.
-
-Requests can be filtered at the path level by appending an absolute or wildcard path to the decryption domains option, following similar wildcard logic to the domains
-themselves. For example:
-
-```js
-// Existing behaviour will be observed, proxying requests to the host 'api.com'.
-const ev = new Evervault('app_uuid', 'api_key', {
-  decryptionDomains: ['api.com']
-});
-
-// Will only proxy requests to host 'api.com' which have a path starting with '/users/'.
-const ev = new Evervault('app_uuid', 'api_key', {
-  decryptionDomains: ['api.com/users/*']
-});
-
-// Will only proxy requests to host 'api.com' which have an exact path of '/settings'.
-const ev = new Evervault('app_uuid', 'api_key', {
-  decryptionDomains: ['api.com/settings']
-});
-```
-
-This change is compatible with the existing hostname wildcard behaviour of `decryptionDomains`.
\ No newline at end of file
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c0144ee7..2b3a7f62 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,33 @@
 # @evervault/sdk
 
+## 6.3.0
+
+### Minor Changes
+
+- 720476d: Extend Relay outbound/forward proxy support in Node to include the ability to filter requests by path using `decryptionDomains`.
+
+  Requests can be filtered at the path level by appending an absolute or wildcard path to the decryption domains option, following similar wildcard logic to the domains
+  themselves. For example:
+
+  ```js
+  // Existing behaviour will be observed, proxying requests to the host 'api.com'.
+  const ev = new Evervault('app_uuid', 'api_key', {
+    decryptionDomains: ['api.com'],
+  });
+
+  // Will only proxy requests to host 'api.com' which have a path starting with '/users/'.
+  const ev = new Evervault('app_uuid', 'api_key', {
+    decryptionDomains: ['api.com/users/*'],
+  });
+
+  // Will only proxy requests to host 'api.com' which have an exact path of '/settings'.
+  const ev = new Evervault('app_uuid', 'api_key', {
+    decryptionDomains: ['api.com/settings'],
+  });
+  ```
+
+  This change is compatible with the existing hostname wildcard behaviour of `decryptionDomains`.
+
 ## 6.2.3
 
 ### Patch Changes
diff --git a/package.json b/package.json
index 0a007a5c..3d8c23de 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@evervault/sdk",
-  "version": "6.2.3",
+  "version": "6.3.0",
   "description": "Node.js SDK for Evervault",
   "main": "lib/index.js",
   "typings": "types/index.d.ts",