From 7aae80a6660405badd921e7d8bb659c9d428d40d Mon Sep 17 00:00:00 2001
From: Mattt <matt.thompson@evervault.com>
Date: Fri, 25 Sep 2026 13:02:57 +0100
Subject: [PATCH] chore(main): move to main branch from master

---
 .changeset/config.json | 2 +-
 CONTRIBUTING.md        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.changeset/config.json b/.changeset/config.json
index 6402ccb..6948d48 100644
--- a/.changeset/config.json
+++ b/.changeset/config.json
@@ -5,7 +5,7 @@
     "fixed": [],
     "linked": [],
     "access": "restricted",
-    "baseBranch": "master",
+    "baseBranch": "main",
     "updateInternalDependencies": "patch",
     "ignore": [],
     "privatePackages": {
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 554198b..69b7461 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -67,7 +67,7 @@ A PR that should land in a release needs a changeset. Run `pnpm changeset`, pick
 level, and describe the change for the changelog. Do not pick major for a breaking change
 without team approval.
 
-Releasing is two steps, both on `master`:
+Releasing is two steps, both on `main`:
 
 1. Merging a PR that contains changesets prompts the bot to open a "New Release" PR that
    bumps the version in `package.json` and `lib/build.gradle`.