chore(repo): change main to master

Author: mandarini

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -91,7 +91,7 @@ body:
       options:
         - label: Follow our [Code of Conduct](https://github.com/supabase/.github/blob/main/CODE_OF_CONDUCT.md)
           required: true
-        - label: Read the [Contributing Guidelines](https://github.com/supabase/supabase-js/blob/main/CONTRIBUTING.md).
+        - label: Read the [Contributing Guidelines](https://github.com/supabase/supabase-js/blob/master/CONTRIBUTING.md).
           required: true
         - label: Read the [docs](https://supabase.com/docs/reference/javascript/introduction).
           required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -40,7 +40,7 @@ body:
       options:
         - label: Follow our [Code of Conduct](https://github.com/supabase/.github/blob/main/CODE_OF_CONDUCT.md)
           required: true
-        - label: Read the [Contributing Guidelines](https://github.com/supabase/supabase-js/blob/main/CONTRIBUTING.md).
+        - label: Read the [Contributing Guidelines](https://github.com/supabase/supabase-js/blob/master/CONTRIBUTING.md).
           required: true
         - label: Read the [docs](https://supabase.com/docs/reference/javascript/introduction).
           required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -29,7 +29,7 @@ Closes #(issue_number) <!-- If applicable -->
 
 <!-- Ensure all items are checked before submitting -->
 
-- [ ] I have read the [Contributing Guidelines](https://github.com/supabase/supabase-js/blob/main/CONTRIBUTING.md)
+- [ ] I have read the [Contributing Guidelines](https://github.com/supabase/supabase-js/blob/master/CONTRIBUTING.md)
 - [ ] My PR title follows the [conventional commit format](https://www.conventionalcommits.org/): `<type>(<scope>): <description>`
 - [ ] I have run `npx nx format` to ensure consistent code formatting
 - [ ] I have added tests for new functionality (if applicable)

.github/workflows/main-ci-release.yml

@@ -34,18 +34,17 @@ jobs:
       contents: read
 
   # ==========================================
-  # CANARY RELEASE (only on main, after all CI passes)
+  # CANARY RELEASE (only on master, after all CI passes)
   # ==========================================
 
   release-canary:
     name: Release Canary
     runs-on: ubuntu-latest
     needs: [ci-core, ci-supabase-js, ci-auth-js-node18]
-    # Only run on main branch pushes, and only if all CI jobs succeeded
+    # Only run on master branch pushes, and only if all CI jobs succeeded
     if: |
-      github.ref == 'refs/heads/main' &&
-      github.event_name == 'push'
-      &&
+      github.ref == 'refs/heads/master' &&
+      github.event_name == 'push' &&
       needs.ci-core.result == 'success' &&
       needs.ci-supabase-js.result == 'success' &&
       needs.ci-auth-js-node18.result == 'success'

CLAUDE.md

@@ -57,14 +57,14 @@ Every change must maintain full backward compatibility. The migration itself int
 
 Uses automated canary releases with batched stable releases:
 
-- **Canary**: Every commit to main → prerelease (e.g., `2.80.1-canary.0`) with `canary` dist-tag
+- **Canary**: Every commit to master → prerelease (e.g., `2.80.1-canary.0`) with `canary` dist-tag
 - **Stable**: Manual promotion of validated canary to `latest` dist-tag
 - **Fixed Versioning**: All packages share identical version numbers (e.g., all at 2.80.0)
 - **Version Line**: Continuing with v2.x.x to maintain ecosystem stability
 
 **Three Release Workflows:**
 
-1. **Canary** (`.github/workflows/main-ci-release.yml`) - Automated on every main commit
+1. **Canary** (`.github/workflows/main-ci-release.yml`) - Automated on every master commit
 2. **Stable** (`.github/workflows/release-stable.yml`) - Manual by repository owners
 3. **Preview** (`.github/workflows/preview-release.yml`) - PR-based testing via pkg.pr.new
 
@@ -262,36 +262,31 @@ Tests run against multiple environments:
 - Requires Docker for integration tests (GoTrue + PostgreSQL)
 - Complex session management logic
 - Security-critical - extra review care needed
-- Default branch: **master**
 - See [auth-js README](packages/core/auth-js/README.md) for details
 
 ### realtime-js
 
 - WebSocket-based, timing-sensitive
 - Mock time in tests when possible
 - No Docker required (uses mock WebSockets)
-- Default branch: **master**
 - See [realtime-js README](packages/core/realtime-js/README.md) for details
 
 ### storage-js
 
 - Requires Docker for integration tests (Storage API + PostgreSQL + Kong)
 - File handling varies by platform
-- Default branch: **main**
 - See [storage-js README](packages/core/storage-js/README.md) for details
 
 ### postgrest-js
 
 - Pure HTTP client, easiest to test
 - Requires Docker for integration tests (PostgREST + PostgreSQL)
-- Default branch: **master**
 - See [postgrest-js README](packages/core/postgrest-js/README.md) for details
 
 ### functions-js
 
 - Simplest library, minimal dependencies
 - Uses testcontainers for Deno relay
-- Default branch: **main**
 - See [functions-js README](packages/core/functions-js/README.md) for details
 
 ## Code Style Guidelines
@@ -487,10 +482,10 @@ cat docs/TESTING.md
 1. **Ensure branch is up to date:**
 
    ```bash
-   git checkout main
-   git pull upstream main
+   git checkout master
+   git pull upstream master
    git checkout your-feature-branch
-   git rebase main
+   git rebase master
    ```
 
 2. **Run all necessary checks:**
@@ -643,7 +638,7 @@ nx test auth-js --testFile=GoTrueClient.test.ts
 **Canary Releases (Automated)**:
 
 ```bash
-# Triggered automatically on every commit to main
+# Triggered automatically on every commit to master
 git commit -m "fix(auth): resolve token issue"
 # → Automatic CI: nx release --tag=canary --yes
 # → Published: 2.80.1-canary.0 to 'canary' dist-tag

CONTRIBUTING.md

@@ -56,7 +56,7 @@ Thank you for your interest in contributing to the Supabase JavaScript client li
 
 ### Making Changes
 
-1. **Create a new branch** from `main`:
+1. **Create a new branch** from `master`:
 
    ```bash
    git checkout -b feature/your-feature-name
@@ -186,13 +186,13 @@ ci(release): add preview package generation
 
 ### Before Submitting
 
-1. **Ensure your branch is up to date** with `main`:
+1. **Ensure your branch is up to date** with `master`:
 
    ```bash
-   git checkout main
-   git pull upstream main
+   git checkout master
+   git pull upstream master
    git checkout your-branch
-   git rebase main
+   git rebase master
    ```
 
 2. **Run the full test suite**:
@@ -283,7 +283,7 @@ npx nx test <package> --coverage
 We automatically generate TypeScript API documentation that is used by the main [Supabase documentation site](https://supabase.com/docs). The process works as follows:
 
 1. **TypeDoc generates JSON specifications** from TypeScript source code
-2. **GitHub Actions publishes** these specs to GitHub Pages on every push to `main`
+2. **GitHub Actions publishes** these specs to GitHub Pages on every push to `master`
 3. **Main Supabase repository** uses these JSON files to generate the official API docs via `make` commands
 
 #### Available Documentation Commands

README.md

@@ -1,5 +1,9 @@
 # Supabase JS Client Libraries
 
+<div align="center">
+[![pkg.pr.new](https://pkg.pr.new/badge/supabase/supabase-js)](https://pkg.pr.new/badge/supabase/supabase-js)
+</div>
+
 _The Supabase JS monorepo containing all the Supabase JavaScript client libraries._
 
 > **📣 Coming from our old repositories?** The `supabase-js` repository has been converted into a monorepo and all other client libraries have been absorbed into it. If you previously contributed to individual repositories like `auth-js`, `postgrest-js`, `realtime-js`, `storage-js`, or `functions-js`, please see our **[Migration Guide](./docs/MIGRATION.md)** to learn about the new structure and workflows.

WARP.md

@@ -256,14 +256,14 @@ nx affected --target=test
 
 ### Library Characteristics
 
-| Library      | Default Branch | Docker Required | Primary Use Case           |
-| ------------ | -------------- | --------------- | -------------------------- |
-| supabase-js  | master         | ❌ No           | Main isomorphic client     |
-| auth-js      | master         | ✅ Yes          | Authentication & user mgmt |
-| postgrest-js | master         | ✅ Yes          | Database queries           |
-| realtime-js  | master         | ❌ No           | Real-time subscriptions    |
-| functions-js | main           | ✅ Yes          | Edge Functions invocation  |
-| storage-js   | main           | ✅ Yes          | File storage operations    |
+| Library      | Docker Required | Primary Use Case           |
+| ------------ | --------------- | -------------------------- |
+| supabase-js  | ❌ No           | Main isomorphic client     |
+| auth-js      | ✅ Yes          | Authentication & user mgmt |
+| postgrest-js | ✅ Yes          | Database queries           |
+| realtime-js  | ❌ No           | Real-time subscriptions    |
+| functions-js | ✅ Yes          | Edge Functions invocation  |
+| storage-js   | ✅ Yes          | File storage operations    |
 
 ## Nx Workspace Features
 
@@ -343,7 +343,7 @@ All packages in this monorepo use **fixed version mode**, meaning they share the
 
 #### 1. Canary Releases (Automated)
 
-**Trigger**: Every commit to `main` branch  
+**Trigger**: Every commit to `master` branch  
 **Workflow**: `.github/workflows/main-ci-release.yml`
 
 - Automatically creates pre-release version (e.g., `2.80.1-canary.0`)
@@ -489,7 +489,7 @@ feat(realtime)!: remove deprecated subscribe method
 
 ### Before Submitting
 
-1. Ensure your branch is up to date with `main`
+1. Ensure your branch is up to date with `master`
 2. Run affected tests: `nx affected --target=test`
 3. Run affected builds: `nx affected --target=build`
 4. Format code: `nx format`

docs/MIGRATION.md

@@ -263,8 +263,8 @@ Commands that weren't available in separate repos:
 # Visualize project dependencies
 npx nx graph
 
-# Build only what changed since main
-npx nx affected --target=build --base=main
+# Build only what changed since master
+npx nx affected --target=build --base=master
 
 # Test only what changed
 npx nx affected --target=test

docs/RELEASE.md

@@ -1,14 +1,14 @@
 # Release Workflows
 
-- [.github/workflows/main-ci-release.yml](.github/workflows/main-ci-release.yml) - Main branch CI & automated canary releases
+- [.github/workflows/main-ci-release.yml](.github/workflows/main-ci-release.yml) - Main CI & automated canary releases
 - [.github/workflows/release-stable.yml](.github/workflows/release-stable.yml) - Manual stable releases
 - [.github/workflows/preview-release.yml](.github/workflows/preview-release.yml) - PR preview releases
 
 ## Overview
 
 This monorepo uses a fixed release model where all packages share a single version number and are released together. There are three types of releases:
 
-1. **Canary Releases** - Automated pre-releases on every commit to main
+1. **Canary Releases** - Automated pre-releases on every commit to master
 2. **Stable Releases** - Manual releases for production use
 3. **Preview Releases** - PR-specific releases for testing changes
 
@@ -17,7 +17,7 @@ This monorepo uses a fixed release model where all packages share a single versi
 ### 🤖 Canary Releases (Automated)
 
 **File:** `main-ci-release.yml`  
-**Trigger:** Every push to `main` branch  
+**Trigger:** Every push to `master` branch  
 **Purpose:** Immediate feedback with pre-release versions
 
 #### What it does
@@ -37,7 +37,7 @@ This monorepo uses a fixed release model where all packages share a single versi
 git commit -m "fix(auth): resolve token refresh issue"
 ```
 
-- Open PR and get it merged to `main`
+- Open PR and get it merged to `master`
 
 - Then:
   → CI runs and passes
@@ -119,7 +119,7 @@ Canary releases are **fully automated**. Simply:
 
 1. Make changes in your feature branch
 2. Use conventional commits with type and scope (e.g., `fix(auth):`, `feat(realtime):`, `chore(repo):`)
-3. Create and merge PR to `main` branch
+3. Create and merge PR to `master` branch
 4. Workflow automatically:
    - Runs CI checks
    - Creates pre-release version
@@ -197,7 +197,7 @@ The workflows rely on `nx.json` release configuration:
 ### For Repository Owners
 
 1. **Release cadence**:
-   - Canary: Automatic on every `main` commit
+   - Canary: Automatic on every `master` commit
    - Stable: Weekly or as needed
    - Major: Coordinate with team and users
 2. **Version strategy**:
@@ -209,7 +209,7 @@ The workflows rely on `nx.json` release configuration:
 
 ### For Emergency Releases
 
-1. **Fix in `main` first** - Apply fix and let canary release
+1. **Fix in `master` first** - Apply fix and let canary release
 2. **Test canary** - Verify fix works in canary version
 3. **Release stable** - Use stable workflow with `patch`
 4. **Document incident** - Update changelog with details