update branch references

Author: yyx990803

src/about/community-guide.md

@@ -54,7 +54,7 @@ You don't have to triage an issue with the goal of fixing it (although that woul
 
 Contributing bug fixes or new features is the most direct form of contribution you can make.
 
-The Vue core repository provides a [contributing guide](https://github.com/vuejs/core/blob/master/.github/contributing.md), which contains pull request guidelines and information regarding build setup and high-level architecture. Other sub-project repositories may also contain its own contribution guide - please make sure to read them before submitting pull requests.
+The Vue core repository provides a [contributing guide](https://github.com/vuejs/core/blob/main/.github/contributing.md), which contains pull request guidelines and information regarding build setup and high-level architecture. Other sub-project repositories may also contain its own contribution guide - please make sure to read them before submitting pull requests.
 
 Bug fixes are welcome at any time. For new features, it is best to discuss the use case and implementation details first in the [RFC repo](https://github.com/vuejs/rfcs/discussions).
 

src/about/releases.md

@@ -22,7 +22,7 @@ The current latest stable version of Vue is <strong>{{ version }}</strong>.
 Checking latest version...
 </p>
 
-A full changelog of past releases is available on [GitHub](https://github.com/vuejs/core/blob/master/CHANGELOG.md).
+A full changelog of past releases is available on [GitHub](https://github.com/vuejs/core/blob/main/CHANGELOG.md).
 
 ## Release Cycle
 

src/api/custom-renderer.md

@@ -82,4 +82,4 @@ Creates a custom renderer. By providing platform-specific node creation and mani
   export * from '@vue/runtime-core'
   ```
 
-  Vue's own `@vue/runtime-dom` is [implemented using the same API](https://github.com/vuejs/core/blob/master/packages/runtime-dom/src/index.ts). For a simpler implementation, check out [`@vue/runtime-test`](https://github.com/vuejs/core/blob/master/packages/runtime-test/src/index.ts) which is a private package for Vue's own unit testing.
+  Vue's own `@vue/runtime-dom` is [implemented using the same API](https://github.com/vuejs/core/blob/main/packages/runtime-dom/src/index.ts). For a simpler implementation, check out [`@vue/runtime-test`](https://github.com/vuejs/core/blob/main/packages/runtime-test/src/index.ts) which is a private package for Vue's own unit testing.

src/api/sfc-script-setup.md

@@ -227,7 +227,7 @@ const post = await fetch(`/api/post/1`).then((r) => r.json())
 In addition, the awaited expression will be automatically compiled in a format that preserves the current component instance context after the `await`.
 
 :::warning Note
-`async setup()` must be used in combination with `Suspense`, which is currently still an experimental feature. We plan to finalize and document it in a future release - but if you are curious now, you can refer to its [tests](https://github.com/vuejs/core/blob/master/packages/runtime-core/__tests__/components/Suspense.spec.ts) to see how it works.
+`async setup()` must be used in combination with `Suspense`, which is currently still an experimental feature. We plan to finalize and document it in a future release - but if you are curious now, you can refer to its [tests](https://github.com/vuejs/core/blob/main/packages/runtime-core/__tests__/components/Suspense.spec.ts) to see how it works.
 :::
 
 ## TypeScript-only Features <sup class="vt-badge ts">TS</sup>

src/api/utility-types.md

@@ -1,7 +1,7 @@
 # Utility Types
 
 :::info
-This page only lists a few commonly used utility types that may need explanation for their usage. For a full list of exported types, consult the [source code](https://github.com/vuejs/core/blob/master/packages/runtime-core/src/index.ts#L131).
+This page only lists a few commonly used utility types that may need explanation for their usage. For a full list of exported types, consult the [source code](https://github.com/vuejs/core/blob/main/packages/runtime-core/src/index.ts#L131).
 :::
 
 ## PropType\<T>

src/guide/best-practices/production-deployment.md

@@ -18,7 +18,7 @@ If you are using Vue without a build tool by loading it from a CDN or self-hoste
 - If using global build (accessing via the `Vue` global): use `vue.global.prod.js`.
 - If using ESM build (accessing via native ESM imports): use `vue.esm-browser.prod.js`.
 
-Consult the [dist file guide](https://github.com/vuejs/core/tree/master/packages/vue#which-dist-file-to-use) for more details.
+Consult the [dist file guide](https://github.com/vuejs/core/tree/main/packages/vue#which-dist-file-to-use) for more details.
 
 ## With Build Tools
 
@@ -27,7 +27,7 @@ Projects scaffolded via `create-vue` (based on Vite) or Vue CLI (based on webpac
 If using a custom setup, make sure that:
 
 1. `vue` resolves to `vue.runtime.esm-bundler.js`.
-2. The [compile time feature flags](https://github.com/vuejs/core/tree/master/packages/vue#bundler-build-feature-flags) are properly configured.
+2. The [compile time feature flags](https://github.com/vuejs/core/tree/main/packages/vue#bundler-build-feature-flags) are properly configured.
 3. <code>process.env<wbr>.NODE_ENV</code> is replaced with `"production"` during build.
 
 Additional references:

src/guide/essentials/template-syntax.md

@@ -160,7 +160,7 @@ Functions called inside binding expressions will be called every time the compon
 
 ### Restricted Globals Access
 
-Template expressions are sandboxed and only have access to a [restricted list of globals](https://github.com/vuejs/core/blob/master/packages/shared/src/globalsWhitelist.ts#L3). The list exposes commonly used built-in globals such as `Math` and `Date`.
+Template expressions are sandboxed and only have access to a [restricted list of globals](https://github.com/vuejs/core/blob/main/packages/shared/src/globalsWhitelist.ts#L3). The list exposes commonly used built-in globals such as `Math` and `Date`.
 
 Globals not explicitly included in the list, for example user-attached properties on `window`, will not be accessible in template expressions. You can, however, explicitly define additional globals for all Vue expressions by adding them to [`app.config.globalProperties`](/api/application.html#app-config-globalproperties).
 

src/guide/extras/composition-api-faq.md

@@ -98,7 +98,7 @@ Code written in Composition API and `<script setup>` is also more efficient and
 
 Yes in terms of stateful logic. When using Composition API, there are only a few options that may still be needed: `props`, `emits`, `name`, and `inheritAttrs`. If using `<script setup>`, then `inheritAttrs` is typically the only option that may require a separate normal `<script>` block.
 
-If you intend to exclusively use Composition API (along with the options listed above), you can shave a few kbs off your production bundle via a [compile-time flag](https://github.com/vuejs/core/tree/master/packages/vue#bundler-build-feature-flags) that drops Options API related code from Vue. Note this also affects Vue components in your dependencies.
+If you intend to exclusively use Composition API (along with the options listed above), you can shave a few kbs off your production bundle via a [compile-time flag](https://github.com/vuejs/core/tree/main/packages/vue#bundler-build-feature-flags) that drops Options API related code from Vue. Note this also affects Vue components in your dependencies.
 
 ### Can I use both APIs together?
 

src/guide/extras/reactivity-transform.md

@@ -12,7 +12,7 @@ Reactivity Transform is a Composition-API-specific feature and requires a build
 
 Ever since the introduction of the Composition API, one of the primary unresolved questions is the use of refs vs. reactive objects. It can be cumbersome to use `.value` everywhere, and it is easy to miss if not using a type system.
 
-[Vue Reactivity Transform](https://github.com/vuejs/core/tree/master/packages/reactivity-transform) is a compile-time transform that allows us to write code like this:
+[Vue Reactivity Transform](https://github.com/vuejs/core/tree/main/packages/reactivity-transform) is a compile-time transform that allows us to write code like this:
 
 ```vue
 <script setup>

src/guide/extras/rendering-mechanism.md

@@ -111,7 +111,7 @@ createElementVNode("div", {
 }, null, 2 /* CLASS */)
 ```
 
-The last argument `2` is a [patch flag](https://github.com/vuejs/core/blob/master/packages/shared/src/patchFlags.ts). An element can have multiple patch flags, which will be merged into a single number. The runtime renderer can then check against the flags using [bitwise operations](https://en.wikipedia.org/wiki/Bitwise_operation) to determine whether it needs to do certain work:
+The last argument `2` is a [patch flag](https://github.com/vuejs/core/blob/main/packages/shared/src/patchFlags.ts). An element can have multiple patch flags, which will be merged into a single number. The runtime renderer can then check against the flags using [bitwise operations](https://en.wikipedia.org/wiki/Bitwise_operation) to determine whether it needs to do certain work:
 
 ```js
 if (vnode.patchFlag & PatchFlags.CLASS /* 2 */) {

src/guide/scaling-up/sfc.md

@@ -52,7 +52,7 @@ That said, we do realize there are scenarios where SFCs can feel like overkill.
 
 ## How It Works
 
-Vue SFC is a framework-specific file format and must be pre-compiled by [@vue/compiler-sfc](https://github.com/vuejs/core/tree/master/packages/compiler-sfc) into standard JavaScript and CSS. A compiled SFC is a standard JavaScript (ES) module - which means with proper build setup you can import an SFC like a module:
+Vue SFC is a framework-specific file format and must be pre-compiled by [@vue/compiler-sfc](https://github.com/vuejs/core/tree/main/packages/compiler-sfc) into standard JavaScript and CSS. A compiled SFC is a standard JavaScript (ES) module - which means with proper build setup you can import an SFC like a module:
 
 ```js
 import MyComponent from './MyComponent.vue'

src/guide/scaling-up/tooling.md

@@ -126,7 +126,7 @@ Custom blocks are compiled into imports to the same Vue file with different requ
 
 ### `@vue/compiler-sfc`
 
-- [Docs](https://github.com/vuejs/core/tree/master/packages/compiler-sfc)
+- [Docs](https://github.com/vuejs/core/tree/main/packages/compiler-sfc)
 
 This package is part of the Vue core monorepo and is always published with the same version as the main `vue` package. It is included as a dependency of the main `vue` package and proxied under `vue/compiler-sfc` so you don't need to install it individually.
 

src/guide/typescript/options-api.md

@@ -224,7 +224,7 @@ declare module 'vue' {
 
 See also:
 
-- [TypeScript unit tests for component type extensions](https://github.com/vuejs/core/blob/master/test-dts/componentTypeExtensions.test-d.tsx)
+- [TypeScript unit tests for component type extensions](https://github.com/vuejs/core/blob/main/test-dts/componentTypeExtensions.test-d.tsx)
 
 ### Type Augmentation Placement
 
@@ -264,4 +264,4 @@ The placement of this augmentation is subject the [same restrictions](#type-augm
 
 See also:
 
-- [TypeScript unit tests for component type extensions](https://github.com/vuejs/core/blob/master/test-dts/componentTypeExtensions.test-d.tsx)
+- [TypeScript unit tests for component type extensions](https://github.com/vuejs/core/blob/main/test-dts/componentTypeExtensions.test-d.tsx)

src/guide/typescript/overview.md

@@ -129,7 +129,7 @@ export default defineComponent({
 })
 ```
 
-See also: [type tests for `defineComponent`](https://github.com/vuejs/core/blob/master/test-dts/defineComponent.test-d.tsx)
+See also: [type tests for `defineComponent`](https://github.com/vuejs/core/blob/main/test-dts/defineComponent.test-d.tsx)
 
 :::tip
 `defineComponent()` also enables type inference for components defined in plain JavaScript.