From 7c3609a8d6d6b1f103955b91f4ea800b272ba722 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 8 Jun 2026 05:00:40 +0000
Subject: [PATCH 1/2] Initial plan


From 0f3f0a8017315a64944775f58884cb857b698326 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 8 Jun 2026 05:02:49 +0000
Subject: [PATCH 2/2] Update README supported TFM to net10.0

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 28961b9..ba88b8e 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@
 
 Getting reference assemblies to use with a `Compilation` is challenging because they are only shipped with development tools. In order to use them in a library, the developer must do the heavy lifting of packaging them up as resources in their library and unpacking them at runtime.
 
-The [Basic.Reference.Assemblies](https://www.nuget.org/packages/Basic.Reference.Assemblies/) library takes care of this heavy lifting and provides reference assemblies for `net8.0`, `netstandard2.0` and `net472` target frameworks. These can be easily integrated into the existing Roslyn APIs.
+The [Basic.Reference.Assemblies](https://www.nuget.org/packages/Basic.Reference.Assemblies/) library takes care of this heavy lifting and provides reference assemblies for `net10.0`, `netstandard2.0` and `net472` target frameworks. These can be easily integrated into the existing Roslyn APIs.
 
 ## Usage Examples