Update all MDX usage to v3 #10106

Jinjiang · 2025-12-03T04:16:11Z

Proposed Changes

Copilot

Pull request overview

This PR updates all MDX dependencies and usage from v1 to v3, modernizing the MDX compilation pipeline across the codebase.

Updates @mdx-js/mdx and @mdx-js/loader to v3.1.1
Replaces custom MDX transpiler with native MDX v3 APIs (compileSync)
Updates webpack loaders and configurations to use MDX v3 loader chain

Reviewed changes

Copilot reviewed 10 out of 11 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
workspace.jsonc	Updates MDX packages to v3.1.1, adds new mdx-v3-options module, removes deprecated mdx-transpiler and mdx-loader components
scripts/find-unused-packages.js	Removes @mdx-js/mdx from whitelist since it's now directly imported
scopes/react/react/webpack/webpack.config.component.dev.ts	Replaces custom mdx-loader with @mdx-js/loader v3 and adds mdx-pre-loader
scopes/react/react/webpack/webpack.config.base.ts	Updates MDX loader configuration to use v3 loader with mdx-v3-options
scopes/mdx/mdx/mdx.doc-reader.ts	Migrates from custom compile API to native compileSync with updated metadata access pattern
scopes/mdx/mdx/mdx.detector.ts	Updates to use native MDX v3 compileSync API and defines ImportSpecifier type locally
scopes/mdx/mdx/mdx.compiler.ts	Switches to native MDX v3 compileSync and uses toString() instead of .contents property
components/legacy/e2e-helper/excluded-fixtures/workspace-with-tsconfig-issue/workspace.jsonc	Updates test fixture dependency versions to match MDX v3 upgrade
.circleci/config.yml	Updates cache keys to reflect new core-aspect-env version (v0.1.0)
.bitmap	Adds environment configuration to all components specifying their env versions

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-04T09:32:52Z

workspace.jsonc

-        "@mdx-js/mdx": "1.6.21",
+        "@mdx-js/loader": "^3.1.1",
+        "@mdx-js/mdx": "^3.1.1",
        "@mdx-js/react": "1.6.22",


The @mdx-js/react package version is still at 1.6.22 (MDX v1), which is inconsistent with the MDX v3 upgrade. This package should be updated to a v3-compatible version (e.g., ^3.1.1) to ensure compatibility with @mdx-js/mdx and @mdx-js/loader which are now at v3.

Suggested change

"@mdx-js/react": "1.6.22",

"@mdx-js/react": "^3.1.1",

Copilot

Pull request overview

Copilot reviewed 18 out of 19 changed files in this pull request and generated 1 comment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-04T10:30:28Z

scopes/workspace/workspace/ui/workspace/use-workspace.ts

    }
  }
-`;
+` as any;


The addition of as any type assertions to GraphQL queries appears to be a workaround for a type compatibility issue introduced by upgrading Apollo Client from an unspecified version to ^3.6.0. While this resolves immediate type errors, it bypasses TypeScript's type checking for GraphQL queries and mutations. Consider using proper TypeScript codegen for GraphQL operations (e.g., @graphql-codegen/cli) or updating to a more recent Apollo Client version that has better TypeScript support, rather than using as any assertions.

Copilot

Pull request overview

Copilot reviewed 20 out of 21 changed files in this pull request and generated 3 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-04T12:48:25Z

scopes/react/react/webpack/webpack.config.component.dev.ts

            {
-              loader: require.resolve('@teambit/mdx.modules.mdx-loader'),
+              loader: require.resolve('@mdx-js/loader'),
+              options: mdxOptions,
+            },
+            {
+              loader: require.resolve('@teambit/mdx.modules.mdx-pre-loader'),
            },


Incorrect loader order for MDX processing

Webpack loaders execute from bottom to top in the use array. The current order has:

@mdx-js/loader (executed second)

@teambit/mdx.modules.mdx-pre-loader (executed first)

This means the pre-loader runs before the main MDX loader, but based on the naming convention, a "pre-loader" should process the file before it's passed to the main loader.

If this is intentional and the pre-loader should run first, consider renaming it to "mdx-post-loader" to clarify the execution order. Otherwise, reverse the order:

{ loader: require.resolve('@teambit/mdx.modules.mdx-pre-loader'), }, { loader: require.resolve('@mdx-js/loader'), options: mdxOptions, },

Copilot · 2025-12-04T12:48:25Z

scopes/react/react/webpack/webpack.config.base.ts

+                  loader: require.resolve('@mdx-js/loader'),
+                  options: mdxOptions,
+                },
+                {
+                  loader: require.resolve('@teambit/mdx.modules.mdx-pre-loader'),
                },


Incorrect loader order for MDX processing

Webpack loaders execute from bottom to top in the use array. The current order has:

@mdx-js/loader (executed second)

@teambit/mdx.modules.mdx-pre-loader (executed first)

This means the pre-loader runs before the main MDX loader, but based on the naming convention, a "pre-loader" should process the file before it's passed to the main loader.

If this is intentional and the pre-loader should run first, consider renaming it to "mdx-post-loader" to clarify the execution order. Otherwise, reverse the order:

{ loader: require.resolve('@teambit/mdx.modules.mdx-pre-loader'), }, { loader: require.resolve('@mdx-js/loader'), options: mdxOptions, },

Suggested change

loader: require.resolve('@mdx-js/loader'),

options: mdxOptions,

},

{

loader: require.resolve('@teambit/mdx.modules.mdx-pre-loader'),

},

loader: require.resolve('@teambit/mdx.modules.mdx-pre-loader'),

},

{

loader: require.resolve('@mdx-js/loader'),

options: mdxOptions,

},

Copilot · 2025-12-04T12:48:26Z

workspace.jsonc

-        "@mdx-js/mdx": "1.6.21",
+        "@mdx-js/loader": "^3.1.1",
+        "@mdx-js/mdx": "^3.1.1",
        "@mdx-js/react": "1.6.22",


Inconsistent MDX package versions

The @mdx-js/mdx and @mdx-js/loader packages have been updated to v3 (^3.1.1), but @mdx-js/react remains at v1 (1.6.22).

For MDX v3, @mdx-js/react should also be updated to v3 to ensure compatibility. The v1 version may not work correctly with MDX v3 compiled output.

Suggested update:

"@mdx-js/react": "^3.1.1"

Suggested change

"@mdx-js/react": "1.6.22",

"@mdx-js/react": "^3.1.1",

Copilot

Pull request overview

Copilot reviewed 21 out of 22 changed files in this pull request and generated 5 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-05T00:43:31Z

scopes/compositions/model/composition-id/humanize.docs.md

 import { humanizeCompositionId } from './humanize'

-```jsx live=true
+```jsx


The removal of live=true from the code block may affect functionality. The live=true attribute typically indicates that the code should be rendered as an interactive example. Verify that this functionality is still supported in MDX v3, or if an alternative approach is needed to maintain the live code preview feature.

Suggested change

```jsx

```jsx live=true

Copilot · 2025-12-05T00:43:31Z

scopes/react/react/react.env.ts

+      { logger: this.logger, worker } as any
+      // { logger: this.logger, worker, devFiles: this.devFiles },


Commented-out code should be removed rather than left in the codebase. The commented line appears to be the correct implementation (including devFiles: this.devFiles), while the active line uses a type assertion (as any) to bypass type checking. Either the commented code should be uncommented and the type issue fixed properly, or it should be removed entirely if it's no longer needed.

Suggested change

{ logger: this.logger, worker } as any

// { logger: this.logger, worker, devFiles: this.devFiles },

{ logger: this.logger, worker, devFiles: this.devFiles }

Copilot · 2025-12-05T00:43:32Z

scopes/react/react/react.env.ts

+      { logger: this.logger, worker } as any
+      // { logger: this.logger, worker, devFiles: this.devFiles },


Commented-out code should be removed rather than left in the codebase. The commented line appears to be the correct implementation (including devFiles: this.devFiles), while the active line uses a type assertion (as any) to bypass type checking. Either the commented code should be uncommented and the type issue fixed properly, or it should be removed entirely if it's no longer needed.

Suggested change

{ logger: this.logger, worker } as any

// { logger: this.logger, worker, devFiles: this.devFiles },

{ logger: this.logger, worker, devFiles: this.devFiles },

Copilot · 2025-12-05T00:43:32Z

workspace.jsonc

        "@teambit/legacy-bit-id": "^1.1.3",
-        "@teambit/mdx.compilers.mdx-transpiler": "^1.0.11",
        "@teambit/mdx.generator.mdx-templates": "^1.0.14",
-        "@teambit/mdx.modules.mdx-loader": "^1.0.15",
+        "@teambit/mdx.modules.mdx-pre-loader": "^0.0.1",
+        "@teambit/mdx.modules.mdx-v3-options": "^0.0.2",


The removal of @teambit/mdx.compilers.mdx-transpiler from the dependency policy should be verified. Since this component is still imported and used in other files (though now replaced with @mdx-js/mdx's compileSync), ensure that all references to this package have been properly removed or updated throughout the codebase to avoid unused dependencies or broken imports.

Copilot · 2025-12-05T00:43:32Z

scopes/harmony/aspect-docs/node/node.mdx

 To use this environment for your components, add it to any of the `variants` in your `workspace.jsonc` file as follows:

-```json title="workspace.jsonc"
+```json


[nitpick] The removal of the title attribute from code blocks may reduce documentation clarity. The title="workspace.jsonc" attribute provided helpful context about which file the code example refers to. Consider whether this information should be retained through other means (e.g., comments or surrounding text) to maintain documentation quality.

Suggested change

```json

```json title="workspace.jsonc"

Copilot

Pull request overview

Copilot reviewed 27 out of 28 changed files in this pull request and generated 7 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-05T01:20:26Z

scopes/react/react/react.env.ts

      { config: jestConfigPath, jest: jestPath },
-      { logger: this.logger, worker, devFiles: this.devFiles }
+      { logger: this.logger, worker } as any
+      // { logger: this.logger, worker, devFiles: this.devFiles },


Similar to line 209, there's commented-out code with uncertainty about the devFiles parameter. This should be resolved - either include the parameter or remove the commented code completely. Having commented code in production suggests incomplete migration.

Suggested change

// { logger: this.logger, worker, devFiles: this.devFiles },

Copilot · 2025-12-05T01:20:27Z

scopes/react/ui/loader-fallback/loader-fallback.docs.mdx

  }
 }
-``` -->
+``` */}


Inconsistent comment syntax in the same file. Lines 24-25 use {/* */} (correct MDX v3 comment syntax for JSX context), while lines 172-229 use the same syntax. However, the closing comment on line 45 is standalone. Ensure all JSX-context comments consistently use the {/* */} syntax.

Suggested change

``` */}

*/}

Copilot · 2025-12-05T01:20:27Z

scopes/mdx/mdx/mdx.detector.ts

+
+type ImportSpecifier = {
+  /**
+   * relative/absolute or module name. e.g. the `y` in the example of `import x from 'y';`
+   */
+  fromModule: string;
+
+  /**
+   * is default import (e.g. `import x from 'y';`)
+   */
+  isDefault?: boolean;
+
+  /**
+   * the name used to identify the module, e.g. the `x` in the example of `import x from 'y';`
+   */
+  identifier?: string;
+};



The ImportSpecifier type is duplicated from what was likely exported by the old MDX transpiler. Consider importing this type from a shared location or the MDX package if available, rather than redefining it locally. This will reduce maintenance burden and potential drift from the canonical definition.

Suggested change

type ImportSpecifier = {

/**

* relative/absolute or module name. e.g. the `y` in the example of `import x from 'y';`

*/

fromModule: string;

/**

* is default import (e.g. `import x from 'y';`)

*/

isDefault?: boolean;

/**

* the name used to identify the module, e.g. the `x` in the example of `import x from 'y';`

*/

identifier?: string;

};

import type { ImportSpecifier } from '@mdx-js/mdx';

Copilot · 2025-12-05T01:20:28Z

scopes/mdx/mdx/mdx.doc-reader.ts

-    const output = await compile(contents.toString('utf-8'), { filepath: path });
-    const metadata = output.getMetadata();
+    const output = compileSync(contents.toString('utf-8'), mdxOptions);
+    const metadata = output.data.frontmatter as any;


The code accesses output.data.frontmatter without checking if output.data exists first. MDX v3's compileSync may not always populate the data property, which could lead to a runtime error. Consider adding a null check: const metadata = output.data?.frontmatter as any || {};

Suggested change

const metadata = output.data.frontmatter as any;

const metadata = output.data?.frontmatter as any || {};

Copilot · 2025-12-05T01:20:28Z

scopes/mdx/mdx/mdx.detector.ts

-    const output = compileSync(source);
-    const imports = output.getImportSpecifiers();
+    const output = compileSync(source, mdxOptions);
+    const imports = output.data.imports as ImportSpecifier[];


Similar to the doc-reader, accessing output.data.imports without checking if output.data exists could cause runtime errors. Add a null check: const imports = output.data?.imports as ImportSpecifier[] || []; to handle cases where the data property might be undefined.

Suggested change

const imports = output.data.imports as ImportSpecifier[];

const imports = output.data?.imports as ImportSpecifier[] || [];

Copilot · 2025-12-05T01:20:28Z

scopes/mdx/mdx/mdx.compiler.ts

+    const afterMdxCompile = mdxCompileSync(fileContent, basicMdxOptions);
    const filePathAfterMdxCompile = this.replaceFileExtToJs(options.filePath);
    const afterBabelCompile = babelTranspileFileContent(
-      afterMdxCompile.contents,
+      afterMdxCompile.toString(),


The MDX v3 compileSync returns a VFile object, not a plain object with a contents property. You should call .toString() method on the result to get the compiled output. However, it appears this is already being done correctly on line 40. Please verify that basicMdxOptions is properly configured for the expected output format.

Copilot

Pull request overview

Copilot reviewed 27 out of 28 changed files in this pull request and generated 3 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-05T01:43:45Z

scopes/react/react/react.main.runtime.ts

    const appType = new ReactAppType('react-app', reactEnv, logger, dependencyResolver);
    const react = new ReactMain(reactEnv, envs, application, appType, dependencyResolver, logger);
-    graphql.register(() => reactSchema(react));
+    graphql.register(() => reactSchema(react) as any);


The GraphQL schema registration is cast to as any, suppressing type checking. This loses TypeScript's type safety benefits.

Investigate why this type assertion is needed and consider defining proper types for the schema instead of using as any.

Copilot · 2025-12-05T01:43:46Z

scopes/mdx/mdx/mdx.doc-reader.ts

-    const output = await compile(contents.toString('utf-8'), { filepath: path });
-    const metadata = output.getMetadata();
+    const output = compileSync(contents.toString('utf-8'), mdxOptions);
+    const metadata = output.data.frontmatter as any;


The MDX compilation result is cast to as any when accessing the frontmatter data. This loses type safety for the metadata extraction.

Consider defining a proper type interface for the MDX compilation output data structure instead of using as any.

Copilot

Pull request overview

Copilot reviewed 27 out of 28 changed files in this pull request and generated 6 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-05T04:54:21Z

scopes/react/react/react.env.ts

        config,
      },
-      { logger: this.logger, worker }
+      // { logger: this.logger, worker } as any,


The commented-out code // { logger: this.logger, worker } as any, should be removed rather than left as a comment. Commented-out code clutters the codebase and can cause confusion about the intended implementation.

Suggested change

// { logger: this.logger, worker } as any,

Copilot · 2025-12-05T04:54:22Z

scopes/mdx/mdx/mdx.doc-reader.ts

-    const output = await compile(contents.toString('utf-8'), { filepath: path });
-    const metadata = output.getMetadata();
+    const output = compileSync(contents.toString('utf-8'), mdxOptions);
+    const metadata = output.data.frontmatter as any;


In MDX v3, the compileSync function returns a VFile object, not a plain object with a data.frontmatter property. The frontmatter is typically extracted through remark plugins like remark-frontmatter and remark-mdx-frontmatter. Without proper plugin configuration in mdxOptions, accessing output.data.frontmatter may result in undefined at runtime, breaking the metadata extraction.

Suggested change

const metadata = output.data.frontmatter as any;

// Ensure mdxOptions includes remark-frontmatter and remark-mdx-frontmatter plugins for frontmatter extraction.

const metadata = (output.data && output.data.frontmatter) ? output.data.frontmatter : {};

Copilot · 2025-12-05T04:54:22Z

scopes/mdx/mdx/mdx.detector.ts

+    const imports = output.data.imports as ImportSpecifier[];
    if (!imports) return [];


In MDX v3, the compileSync function returns a VFile object which needs to be converted to a string using .toString() or accessed via .value property. The data.imports property may not exist unless specific plugins are configured to populate it. The expected structure for imports in MDX v3 is different from v1, and without proper plugin configuration, this will likely fail at runtime.

Suggested change

const imports = output.data.imports as ImportSpecifier[];

if (!imports) return [];

const imports = Array.isArray(output.data?.imports) ? output.data.imports as ImportSpecifier[] : [];

if (!imports.length) return [];

Copilot · 2025-12-05T04:54:23Z

scopes/react/react/webpack/webpack.config.base.ts

 // Make sure the mdx-loader is a dependency
-import '@teambit/mdx.modules.mdx-loader';
-
+// eslint-disable-next-line import/no-unresolved


The /* eslint-disable import/no-unresolved */ comment suggests there's an unresolved import issue with @mdx-js/loader. This typically indicates that the package is not properly installed or the types are not available. This should be resolved rather than suppressed, as it may cause issues in development and could indicate a missing dependency.

Suggested change

// eslint-disable-next-line import/no-unresolved

Copilot · 2025-12-05T04:54:23Z

scopes/workspace/workspace/ui/workspace/use-workspace.ts

    }
  }
-`;
+` as any;


Multiple as any type assertions are being added to GraphQL query definitions. While this might resolve immediate TypeScript compilation issues related to the MDX v3 upgrade, it bypasses type safety and could hide real type errors. Consider using proper typing with GraphQL code generation tools like graphql-code-generator or explicitly typing the queries instead of using as any.

Copilot · 2025-12-05T04:54:23Z

scopes/mdx/aspect-docs/mdx/mdx.mdx


-```jsx live=true
+```jsx live="true"
 <LoginForm><LoginForm/>


The closing tag syntax is incorrect. It should be <LoginForm /> with a space before the closing slash, not <LoginForm/> (which is also missing the opening tag based on line 24). This appears to be a typo that would cause a syntax error.

Suggested change

<LoginForm><LoginForm/>

<LoginForm />

Jinjiang added 2 commits December 3, 2025 12:48

chore: update envs to remove mdx v1

e530934

chore: update mdx-loader and mdx-transpiler into mdx v3

a443eab

Jinjiang force-pushed the jinjiang/mdx-update-20251202 branch from 25ffdd0 to a443eab Compare December 3, 2025 04:52

Jinjiang added 3 commits December 3, 2025 13:19

chore: update env cache key in circleci config

8aca136

chore: update @apollo/client to fix type conflicts

65fbf7c

chore: debug graphql version conflicts

6e6ded9

Copilot AI review requested due to automatic review settings December 4, 2025 09:29

Copilot started reviewing on behalf of Jinjiang December 4, 2025 09:29 View session

Copilot finished reviewing on behalf of Jinjiang December 4, 2025 09:31

Copilot AI reviewed Dec 4, 2025

View reviewed changes

chore: fix graphql version conflicts

c059a51

Copilot AI review requested due to automatic review settings December 4, 2025 10:26

Jinjiang force-pushed the jinjiang/mdx-update-20251202 branch from db398fd to c059a51 Compare December 4, 2025 10:26

Copilot started reviewing on behalf of Jinjiang December 4, 2025 10:27 View session

Copilot finished reviewing on behalf of Jinjiang December 4, 2025 10:29

Copilot AI reviewed Dec 4, 2025

View reviewed changes

Jinjiang added 2 commits December 4, 2025 20:28

chore: debug bit ci pr

5db3ca6

chore: fix react/react type error

ca366ed

Copilot AI review requested due to automatic review settings December 4, 2025 12:44

Copilot started reviewing on behalf of Jinjiang December 4, 2025 12:44 View session

Copilot finished reviewing on behalf of Jinjiang December 4, 2025 12:46

Copilot AI reviewed Dec 4, 2025

View reviewed changes

Jinjiang added 2 commits December 5, 2025 08:35

chore: fix react/react type error

1fe7e0b

chore: debug bit ci pr

891eff5

Copilot AI review requested due to automatic review settings December 5, 2025 00:39

Copilot started reviewing on behalf of Jinjiang December 5, 2025 00:40 View session

Copilot finished reviewing on behalf of Jinjiang December 5, 2025 00:42

Copilot AI reviewed Dec 5, 2025

View reviewed changes

Copilot AI review requested due to automatic review settings December 5, 2025 01:15

Jinjiang force-pushed the jinjiang/mdx-update-20251202 branch from 8e204ba to 6c7edc9 Compare December 5, 2025 01:15

Copilot started reviewing on behalf of Jinjiang December 5, 2025 01:16 View session

Copilot finished reviewing on behalf of Jinjiang December 5, 2025 01:18

Copilot AI reviewed Dec 5, 2025

View reviewed changes

Jinjiang force-pushed the jinjiang/mdx-update-20251202 branch from 6c7edc9 to 0506006 Compare December 5, 2025 01:36

Copilot AI review requested due to automatic review settings December 5, 2025 01:38

Jinjiang force-pushed the jinjiang/mdx-update-20251202 branch from 0506006 to 731502c Compare December 5, 2025 01:38

Copilot started reviewing on behalf of Jinjiang December 5, 2025 01:39 View session

Copilot finished reviewing on behalf of Jinjiang December 5, 2025 01:41

Copilot AI reviewed Dec 5, 2025

View reviewed changes

chore: debug bit ci pr

59c7ef8

Jinjiang force-pushed the jinjiang/mdx-update-20251202 branch from 731502c to 59c7ef8 Compare December 5, 2025 03:19

chore: debug bit ci pr

fcfb356

Copilot AI review requested due to automatic review settings December 5, 2025 04:50

Copilot started reviewing on behalf of Jinjiang December 5, 2025 04:50 View session

Copilot finished reviewing on behalf of Jinjiang December 5, 2025 04:52

Copilot AI reviewed Dec 5, 2025

View reviewed changes

fix(bit): handle URL objects in filesystem read debug output

cde2250

		{ logger: this.logger, worker } as any
		// { logger: this.logger, worker, devFiles: this.devFiles },

	{ logger: this.logger, worker } as any
	// { logger: this.logger, worker, devFiles: this.devFiles },
	{ logger: this.logger, worker, devFiles: this.devFiles }

	const metadata = output.data.frontmatter as any;
	const metadata = output.data?.frontmatter as any \|\| {};

	const imports = output.data.imports as ImportSpecifier[];
	const imports = output.data?.imports as ImportSpecifier[] \|\| [];

	const metadata = output.data.frontmatter as any;
	// Ensure mdxOptions includes remark-frontmatter and remark-mdx-frontmatter plugins for frontmatter extraction.
	const metadata = (output.data && output.data.frontmatter) ? output.data.frontmatter : {};

		const imports = output.data.imports as ImportSpecifier[];
		if (!imports) return [];

Update all MDX usage to v3 #10106

Are you sure you want to change the base?

Update all MDX usage to v3 #10106

Uh oh!

Conversation

Jinjiang commented Dec 3, 2025

Proposed Changes

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview