Remove build scripts that no longer have any use, and modify urls/bra…

…nchnames

.changeset/config.json

@@ -1,12 +1,12 @@
 {
   "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
   "access": "public",
-  "baseBranch": "master",
+  "baseBranch": "main",
   "bumpVersionsWithWorkspaceProtocolOnly": true,
   "changelog": [
     "@changesets/changelog-github",
     {
-      "repo": "solana-labs/solana-web3.js"
+      "repo": "anza-xyz/solana-web3.js"
     }
   ],
   "fixed": [["@solana/!({*-impl,build-scripts,test-*,tsconfig})"]],

.github/dependabot.yml

@@ -5,17 +5,6 @@
 
 version: 2
 updates:
-  - target-branch: 'maintenance/v1.x'
-    package-ecosystem: 'npm'
-    directory: '/'
-    schedule:
-      interval: daily
-      time: '01:00'
-      timezone: America/Los_Angeles
-    labels:
-      - 'automerge'
-    commit-message:
-      prefix: 'chore:'
   - package-ecosystem: 'npm'
     directory: '/'
     schedule:

.github/label-actions.yml

@@ -21,7 +21,7 @@ question:
       ---
 
       _This
-      [automated message](https://github.com/solana-labs/solana-web3.js/blob/master/.github/label-actions.yml)
+      [automated message](https://github.com/anza-xyz/solana-web3.js/blob/main/.github/label-actions.yml)
       is a result of having added the ‘question’ tag_.
 
     # Close the issue

.github/workflows/bundlesize.yml

@@ -2,7 +2,8 @@ name: Compare bundle size
 
 on:
   push:
-    branches: [master]
+    branches:
+      - main
   pull_request:
     types: [synchronize, opened, reopened]
 

.github/workflows/publish-canary-releases.yml

@@ -3,10 +3,10 @@ name: Publish Canary Releases
 on:
   workflow_dispatch:
     branches:
-      - master
+      - main
   push:
     branches:
-      - master
+      - main
 
 env:
   # Among other things, opts out of Turborepo telemetry

.github/workflows/publish-packages.yml

@@ -3,10 +3,10 @@ name: Publish Packages
 on:
   workflow_dispatch:
     branches:
-      - master
+      - main
   push:
     branches:
-      - master
+      - main
 
 env:
   # Among other things, opts out of Turborepo telemetry

README.md

@@ -1056,7 +1056,7 @@ export const getMyTokenCodec = (): Codec<MyTokenArgs, MyToken> =>
     combineCodec(getMyTokenEncoder(), getMyTokenDecoder());
 ```
 
-You can read more about codecs in [the official Codec documentation](https://github.com/solana-labs/solana-web3.js/blob/master/packages/codecs/README.md).
+You can read more about codecs in [the official Codec documentation](https://github.com/anza-xyz/solana-web3.js/blob/main/packages/codecs/README.md).
 
 ## Type-Safety
 
@@ -1224,7 +1224,7 @@ Here’s how to convert legacy transaction objects to the new library’s transa
 const modernTransaction = fromVersionedTransaction(classicTransaction);
 ```
 
-To see more conversions supported by `@solana/compat`, you can check out the package’s [README on GitHub](https://github.com/solana-labs/solana-web3.js/blob/master/packages/compat/README.md).
+To see more conversions supported by `@solana/compat`, you can check out the package’s [README on GitHub](https://github.com/anza-xyz/solana-web3.js/blob/main/packages/compat/README.md).
 
 ## Program Clients
 
@@ -1448,13 +1448,13 @@ expect(result).toMatchObject({
 });
 ```
 
-See more in the package’s [README on GitHub](https://github.com/solana-labs/solana-web3.js/tree/master/packages/rpc-graphql).
+See more in the package’s [README on GitHub](https://github.com/anza-xyz/solana-web3.js/tree/main/packages/rpc-graphql).
 
 ## Development
 
 You can see all development of this library and associated GraphQL tooling in the web3.js repository on GitHub.
 
--   https://github.com/solana-labs/solana-web3.js
+-   https://github.com/anza-xyz/solana-web3.js
 
 You can follow along with program client generator development in the `@solana-program` org and the `@codama-idl/codama` repository.
 

SECURITY.md

@@ -9,7 +9,7 @@
 
 **DO NOT CREATE A GITHUB ISSUE** to report a security problem.
 
-Instead please use this [Report a Vulnerability](https://github.com/solana-labs/solana-web3.js/security/advisories/new) link. Provide a helpful title, detailed description of the vulnerability and an exploit proof-of-concept. Speculative submissions without proof-of-concept will be closed with no further consideration.
+Instead please use this [Report a Vulnerability](https://github.com/anza-xyz/solana-web3.js/security/advisories/new) link. Provide a helpful title, detailed description of the vulnerability and an exploit proof-of-concept. Speculative submissions without proof-of-concept will be closed with no further consideration.
 
 If you haven't done so already, please **enable two-factor auth** in your GitHub account.
 
@@ -27,23 +27,23 @@ In case an incident is discovered or reported, the following process will be fol
 
 ### 1. Accept the new report
 
-In response to a newly reported security problem, a member of the `solana-labs/admins` group will accept the report to turn it into a draft advisory. The `solana-labs/security-incident-response` group should be added to the draft security advisory, and create a private fork of the repository (grey button towards the bottom of the page) if necessary.
+In response to a newly reported security problem, a member of the `anza-xyz/core-contributors` group will accept the report to turn it into a draft advisory. The `anza-xyz/security-incident-response` group should be added to the draft security advisory, and create a private fork of the repository (grey button towards the bottom of the page) if necessary.
 
 If the advisory is the result of an audit finding, follow the same process as above but add the auditor's github user(s) and begin the title with "[Audit]".
 
-If the report is out of scope, a member of the `solana-labs/admins` group will comment as such and then close the report.
+If the report is out of scope, a member of the `anza-xyz/core-contributors` group will comment as such and then close the report.
 
 ### 2. Triage
 
-Within the draft security advisory, discuss and determine the severity of the issue. If necessary, members of the `solana-labs/security-incident-response` group may add other github users to the advisory to assist. If it is determined that this is not a critical issue then the advisory should be closed and if more follow-up is required a normal Solana public github issue should be created.
+Within the draft security advisory, discuss and determine the severity of the issue. If necessary, members of the `anza-xyz/security-incident-response` group may add other github users to the advisory to assist. If it is determined that this is not a critical issue then the advisory should be closed and if more follow-up is required a normal Solana public github issue should be created.
 
 ### 3. Prepare Fixes
 
-Prepare a fix for the issue and push them to master in the private repository associated with the draft security advisory. There is no CI available in the private repository so you must build from source and manually verify fixes. Code review from the reporter is ideal, as well as from multiple members of the core development team.
+Prepare a fix for the issue and push them to `main` in the private repository associated with the draft security advisory. There is no CI available in the private repository so you must build from source and manually verify fixes. Code review from the reporter is ideal, as well as from multiple members of the core development team.
 
 ### 4. Ship the patch
 
-Once the fix is accepted, a member of the solana-labs/security-incident-response group should prepare a patch using [`pnpm patch`](https://pnpm.io/cli/patch), [`yarn patch`](https://yarnpkg.com/cli/patch), and [`patch-package`](https://www.npmjs.com/package/patch-package) for developers still using `npm`. Post the patch to an unlisted [GitHub Gist](https://gist.github.com) and disseminate patch instructions privately to as many vulnerable applications as possible.
+Once the fix is accepted, a member of the anza-xyz/security-incident-response group should prepare a patch using [`pnpm patch`](https://pnpm.io/cli/patch), [`yarn patch`](https://yarnpkg.com/cli/patch), and [`patch-package`](https://www.npmjs.com/package/patch-package) for developers still using `npm`. Post the patch to an unlisted [GitHub Gist](https://gist.github.com) and disseminate patch instructions privately to as many vulnerable applications as possible.
 
 ### 5. Public Disclosure and Release
 

examples/react-app/README.md

@@ -2,8 +2,6 @@
 
 This is an example of how to use `@solana/web3.js` and `@solana/react` to build a React web application.
 
-The latest version of this code is automatically deployed to https://solana-labs.github.io/solana-web3.js/example/
-
 ## Features
 
 -   Connects to browser wallets that support the Wallet Standard; one or more at a time

packages/accounts/README.md

@@ -11,7 +11,7 @@
 
 # @solana/accounts
 
-This package contains types and helper methods for representing, fetching and decoding Solana accounts. It can be used standalone, but it is also exported as part of the Solana JavaScript SDK [`@solana/web3.js@next`](https://github.com/solana-labs/solana-web3.js/tree/master/packages/library).
+This package contains types and helper methods for representing, fetching and decoding Solana accounts. It can be used standalone, but it is also exported as part of the Solana JavaScript SDK [`@solana/web3.js@next`](https://github.com/anza-xyz/solana-web3.js/tree/main/packages/library).
 
 It provides a unified definition of a Solana account regardless of how it was retrieved and can represent both encoded and decoded accounts. It also introduces the concept of a `MaybeAccount` which represents a fetched account that may or may not exist on-chain whilst keeping track of its address in both cases.
 

packages/accounts/package.json

@@ -61,10 +61,10 @@
     "license": "MIT",
     "repository": {
         "type": "git",
-        "url": "https://github.com/solana-labs/solana-web3.js"
+        "url": "https://github.com/anza-xyz/solana-web3.js"
     },
     "bugs": {
-        "url": "http://github.com/solana-labs/solana-web3.js/issues"
+        "url": "http://github.com/anza-xyz/solana-web3.js/issues"
     },
     "browserslist": [
         "supports bigint and not dead",

packages/addresses/README.md

@@ -11,7 +11,7 @@
 
 # @solana/addresses
 
-This package contains utilities for generating account addresses. It can be used standalone, but it is also exported as part of the Solana JavaScript SDK [`@solana/web3.js@next`](https://github.com/solana-labs/solana-web3.js/tree/master/packages/library).
+This package contains utilities for generating account addresses. It can be used standalone, but it is also exported as part of the Solana JavaScript SDK [`@solana/web3.js@next`](https://github.com/anza-xyz/solana-web3.js/tree/main/packages/library).
 
 ## Types
 

packages/addresses/package.json

@@ -61,10 +61,10 @@
     "license": "MIT",
     "repository": {
         "type": "git",
-        "url": "https://github.com/solana-labs/solana-web3.js"
+        "url": "https://github.com/anza-xyz/solana-web3.js"
     },
     "bugs": {
-        "url": "http://github.com/solana-labs/solana-web3.js/issues"
+        "url": "http://github.com/anza-xyz/solana-web3.js/issues"
     },
     "browserslist": [
         "supports bigint and not dead",

packages/assertions/package.json

@@ -61,10 +61,10 @@
     "license": "MIT",
     "repository": {
         "type": "git",
-        "url": "https://github.com/solana-labs/solana-web3.js"
+        "url": "https://github.com/anza-xyz/solana-web3.js"
     },
     "bugs": {
-        "url": "http://github.com/solana-labs/solana-web3.js/issues"
+        "url": "http://github.com/anza-xyz/solana-web3.js/issues"
     },
     "browserslist": [
         "supports bigint and not dead",