Repository navigation
Conversation
Updated [csharpier](https://github.com/belav/csharpier) from 1.3.0 to 1.4.0. <details> <summary>Release notes</summary> _Sourced from [csharpier's releases](https://github.com/belav/csharpier/releases)._ ## 1.4.0 ## Breaking Changes ### Drop support for net8.0 and net9.0 [#1888](belav/csharpier#1888) CSharpier and CSharpier.MsBuild now target `net10.0` and `net11.0`. CSharpier.Core targets `net10.0`, `net11.0` and `netstandard2.0`. ## What's Changed ### Feature: Support for .NET 11 and C# 15 [#1888](belav/csharpier#1888) CSharpier now supports the new syntax in C# 15. ```c# public union Pet(Cat, Dog, Bird); public closed record GateState; HashSet<string> set = [with(StringComparer.OrdinalIgnoreCase), "Hello", "HELLO", "hello"]; outer: for (int row = 0; row < grid.Height; row++) { for (int column = 0; column < grid.Width; column++) { if (grid[row, column].IsBlocked) { continue outer; } if (grid[row, column].IsGoal) { break outer; } } } ``` ### Feature: Avoid chopping single trailing lambda [#1865](belav/csharpier#1865) When the last argument is a lambda with a block body, and the arguments up to and including the `=>` fit on one line, CSharpier now keeps them on the same line as the method name. ```c# // input & expected output logging.AddFile(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "server{0}.log"), o => { o.MaxRollingFiles = 1; }); // 1.3.0 logging.AddFile( Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "server{0}.log"), o => { o.MaxRollingFiles = 1; } ); ``` ... (truncated) ## 1.3.11-beta1 ## 1.3.6 # 1.3.6 ## What's Changed #### Fix bug where 2nd instance of VSCode was not able to format code [#784](belav/csharpier#784) Thanks to @BenasB for reporting the issue Commits viewable in [compare view](belav/csharpier@1.3.0...1.4.0). </details> Updated [Microsoft.Extensions.Logging.Abstractions](https://github.com/dotnet/dotnet) from 10.0.14 to 11.0.0. <details> <summary>Release notes</summary> _Sourced from [Microsoft.Extensions.Logging.Abstractions's releases](https://github.com/dotnet/dotnet/releases)._ ## 10.0.404 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.404` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.404/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.404/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## Important Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.404-servicing.26529.119.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID `2001:2001`, while GitHub’s automatically generated archives use `0:0`. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail. ## 10.0.403 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.403` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.403/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.403/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.402 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.402` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.402/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.402/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.401 [Release](https://github.com/dotnet/core/releases/tag/v10.0.12) ## What's Changed * [release/10.0.4xx] Source code updates from dotnet/sdk by @dotnet-maestro[bot] in dotnet/dotnet#8011 * [release/10.0.4xx] Source code updates from dotnet/sdk by @dotnet-maestro[bot] in dotnet/dotnet#8037 * [release/10.0.4xx] Source code updates from dotnet/sdk by @dotnet-maestro[bot] in dotnet/dotnet#8038 * Update Source-Build SDK Diff Tests Baselines and Exclusions by @dotnet-sb-bot in dotnet/dotnet#7754 * [release/10.0.4xx] Source code updates from dotnet/arcade by @dotnet-maestro[bot] in dotnet/dotnet#8101 * [release/10.0.4xx] Source code updates from dotnet/source-build-assets by @dotnet-maestro[bot] in dotnet/dotnet#8104 * [release/10.0.4xx] Source code updates from dotnet/msbuild by @dotnet-maestro[bot] in dotnet/dotnet#8142 * [release/10.0.4xx] Source code updates from dotnet/sdk by @dotnet-maestro[bot] in dotnet/dotnet#8132 * [release/10.0.4xx] Source code updates from dotnet/source-build-assets by @dotnet-maestro[bot] in dotnet/dotnet#8127 * [release/10.0.4xx] Source code updates from dotnet/arcade by @dotnet-maestro[bot] in dotnet/dotnet#8156 * [release/10.0.4xx] Source code updates from dotnet/roslyn by @dotnet-maestro[bot] in dotnet/dotnet#8148 * [release/10.0.4xx] Source code updates from dotnet/sdk by @dotnet-maestro[bot] in dotnet/dotnet#8176 * [release/10.0.4xx] Source code updates from dotnet/arcade by @dotnet-maestro[bot] in dotnet/dotnet#8171 * [release/10.0.4xx] Source code updates from dotnet/scenario-tests by @dotnet-maestro[bot] in dotnet/dotnet#8092 * [release/10.0.4xx] Fix IdentityModel shared-components source build by @mthalman in dotnet/dotnet#8189 * [release/10.0.4xx] Source code updates from nuget/nuget.client by @dotnet-maestro[bot] in dotnet/dotnet#8201 * [release/10.0.4xx] Allow submodule changes when reseting submodules by @github-actions[bot] in dotnet/dotnet#8223 * [release/10.0.4xx] Source code updates from dotnet/roslyn by @dotnet-maestro[bot] in dotnet/dotnet#8215 * [release/10.0.4xx] Source code updates from dotnet/arcade by @dotnet-maestro[bot] in dotnet/dotnet#8210 * [release/10.0.4xx] Cloak SignatureCycle2 binary from VMR by @mthalman in dotnet/dotnet#8226 * [release/10.0.4xx] Ignore spurious SBoM warnings by @akoeplinger in dotnet/dotnet#8165 * [release/10.0.4xx] Source code updates from dotnet/arcade by @dotnet-maestro[bot] in dotnet/dotnet#8231 * Update to the 10.0.11 August runtimes from build 324376 by @mthalman in dotnet/dotnet#8259 * Merging internal commits for release/10.0.4xx by @dotnet-bot in dotnet/dotnet#8242 * [release/10.0.4xx] Source code updates from dotnet/arcade by @dotnet-maestro[bot] in dotnet/dotnet#8278 * [release/10.0.4xx] Source code updates from dotnet/arcade by @dotnet-maestro[bot] in dotnet/dotnet#8304 * [release/10.0.4xx] Source code updates from dotnet/roslyn by @dotnet-maestro[bot] in dotnet/dotnet#8347 * [release/10.0.4xx] Remove duplicate dependency from scenario-tests by @dkurepa in dotnet/dotnet#8350 * [release/10.0.4xx] Source code updates from dotnet/sourcelink by @dotnet-maestro[bot] in dotnet/dotnet#8344 * [release/10.0.4xx] Source code updates from dotnet/templating by @dotnet-maestro[bot] in dotnet/dotnet#8354 * [release/10.0.4xx] Fix SignCheckExclusionsFile.txt to allow signed hotreload .js file by @github-actions[bot] in dotnet/dotnet#8383 * [release/10.0.4xx] Remove TSA bug filing from pipelines by @akoeplinger in dotnet/dotnet#8389 * [release/10.0.4xx] Source code updates from dotnet/arcade by @dotnet-maestro[bot] in dotnet/dotnet#8396 * [release/10.0.4xx] [release/10.0.1xx] Update binskim lastModifiedDate in PipelineAutobaseliningConfig.yml by @github-actions[bot] in dotnet/dotnet#8408 * [release/10.0.4xx] Fix SignCheckExclusionsFile.txt for .js in source-build artifacts by @github-actions[bot] in dotnet/dotnet#8405 * [release/10.0.4xx] Source code updates from dotnet/templating by @dotnet-maestro[bot] in dotnet/dotnet#8419 * [release/10.0.4xx] Source code updates from dotnet/templating by @dotnet-maestro[bot] in dotnet/dotnet#8422 * [release/10.0.4xx] Source code updates from dotnet/msbuild by @dotnet-maestro[bot] in dotnet/dotnet#8429 * [release/10.0.4xx] Source code updates from dotnet/source-build-assets by @dotnet-maestro[bot] in dotnet/dotnet#8313 * [release/10.0.4xx] Source code updates from dotnet/templating by @dotnet-maestro[bot] in dotnet/dotnet#8452 * [release/10.0.4xx] Source code updates from dotnet/source-build-assets by @dotnet-maestro[bot] in dotnet/dotnet#8453 * [release/10.0.4xx] Source code updates from dotnet/msbuild by @dotnet-maestro[bot] in dotnet/dotnet#8469 * [release/10.0.4xx] Source code updates from dotnet/fsharp by @dotnet-maestro[bot] in dotnet/dotnet#8521 * [release/10.0.4xx] Source code updates from dotnet/arcade by @dotnet-maestro[bot] in dotnet/dotnet#8574 * [release/10.0.4xx] Bump patch version to 10.0.401 by @vseanreesermsft in dotnet/dotnet#8577 ... (truncated) ## 10.0.400 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.400` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.400/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.400/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.303 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.303` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.303/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.303/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.302 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.302` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.302/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.302/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.301 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.301` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.301/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.301/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.300 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.300` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.300/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.300/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.204 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.204` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.204/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.204/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.203 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.203` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.203/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.203/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.202 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.202` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.202/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.202/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.201 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.201` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.201/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.201/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.200 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.200` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.200/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.200/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.115 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.115` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.115/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.115/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## Important Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.115-servicing.26529.108.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signature was generated from a build-produced source archive with ownership normalized to UID/GID `2001:2001`, while GitHub’s automatically generated archive uses `0:0`. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail. ## 10.0.114 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.114` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.114/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.114/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## Important Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.114-servicing.26522.126.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID `2001:2001`, while GitHub’s automatically generated archives use `0:0`. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail. ## 10.0.113 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.113` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.113/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.113/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.112 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.112` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.112/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.112/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.111 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.111` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.111/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.111/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.110 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.110` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.110/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.110/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.109 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.109` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.109/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.109/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.108 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.108` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.108/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.108/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.107 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.107` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.107/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.107/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.106 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.106` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.106/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.106/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.105 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.105` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.105/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.105/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.104 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.104` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.104/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.104/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.103 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.103` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.103/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.103/README.md#building-from-released-sources). Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.102-sb1 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.102-sb1` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.102-sb1/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.102-sb1/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.101 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.101` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.101/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.101/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.100 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.100` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.100/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.100/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 To produce artifacts with the .NET 10 GA version strings, users must pass the branding argument to the build: `--branding rtm`. ## 10.0.100-rc.2.25502.107 You can build .NET 10.0 RC 2 from the repository by cloning the release tag `v10.0.100-rc.2.25502.107` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.100-rc.2.25502.107/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.100-rc.2.25502.107/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 Note: GitHub automatically generates the "Source code (tar.gz/zip)" archives included in this release. Please download the official source code from: - [dotnet-source-10.0.100-rc.2.25502.107.tar.gz](https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.100-rc.2.25502.107.tar.gz) - [dotnet-source-10.0.100-rc.2.25502.107.zip](https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.100-rc.2.25502.107.zip) ## 10.0.100-rc.1.25451.107 <!-- This file is a template for a GitHub release notes post. --> <!-- The line prefixed by 'Title:' will be submitted as the title of the release notes, and the rest of the file will be submitted as the body. --> You can build .NET 10.0 RC 1 from the repository by cloning the release tag `v10.0.100-rc.1.25451.107` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.100-rc.1.25451.107/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.100-rc.1.25451.107/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.100-preview.7.25380.108 <!-- This file is a template for a GitHub release notes post. --> <!-- The line prefixed by 'Title:' will be submitted as the title of the release notes, and the rest of the file will be submitted as the body. --> You can build .NET 10.0 Preview 7 from the repository by cloning the release tag `v10.0.100-preview.7.25380.108` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.100-preview.7.25380.108/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.100-preview.7.25380.108/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 Commits viewable in [compare view](https://github.com/dotnet/dotnet/commits). </details> Updated [Microsoft.NET.Test.Sdk](https://github.com/microsoft/vstest) from 18.11.0 to 18.12.0. <details> <summary>Release notes</summary> _Sourced from [Microsoft.NET.Test.Sdk's releases](https://github.com/microsoft/vstest/releases)._ No release notes found for this version range. Commits viewable in [compare view](https://github.com/microsoft/vstest/commits). </details> Updated [Microsoft.SourceLink.GitHub](https://github.com/dotnet/dotnet) from 10.0.403 to 11.0.100. <details> <summary>Release notes</summary> _Sourced from [Microsoft.SourceLink.GitHub's releases](https://github.com/dotnet/dotnet/releases)._ ## 11.0.100 You can build .NET 11.0 from the repository by cloning the release tag `v11.0.100` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## Important Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-11.0.100-rtm.26529.118.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID `2001:2001`, while GitHub’s automatically generated archives use `0:0`. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail. ## 11.0.100-rc.3.26522.148 You can build .NET 11.0 RC 3 from the repository by cloning the release tag `v11.0.100-rc.3.26522.148` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-rc.3.26522.148/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-rc.3.26522.148/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## Important Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-11.0.100-rc.3.26522.148.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID `2001:2001`, while GitHub’s automatically generated archives use `0:0`. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail. ## 11.0.100-rc.2.26504.105 You can build .NET 11.0 RC 2 from the repository by cloning the release tag `v11.0.100-rc.2.26504.105` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-rc.2.26504.105/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-rc.2.26504.105/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 11.0.100-rc.1.26425.128 You can build .NET 11.0 RC 1 from the repository by cloning the release tag `v11.0.100-rc.1.26425.128` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-rc.1.26425.128/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-rc.1.26425.128/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 11.0.100-preview.7.26381.103 You can build .NET 11.0 Preview 7 from the repository by cloning the release tag `v11.0.100-preview.7.26381.103` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.7.26381.103/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.7.26381.103/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 11.0.100-preview.6.26359.118 You can build .NET 11.0 Preview 6 from the repository by cloning the release tag `v11.0.100-preview.6.26359.118` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.6.26359.118/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.6.26359.118/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 11.0.100-preview.5.26302.115 You can build .NET 11.0 Preview 5 from the repository by cloning the release tag `v11.0.100-preview.5.26302.115` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.5.26302.115/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.5.26302.115/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 11.0.100-preview.4.26230.115 You can build .NET 11.0 Preview 4 from the repository by cloning the release tag `v11.0.100-preview.4.26230.115` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.4.26230.115/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.4.26230.115/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 11.0.100-preview.3.26207.106 You can build .NET 11.0 Preview 3 from the repository by cloning the release tag `v11.0.100-preview.3.26207.106` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.3.26207.106/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.3.26207.106/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 11.0.100-preview.2.26159.112 You can build .NET 11.0 Preview 2 from the repository by cloning the release tag `v11.0.100-preview.2.26159.112` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.2.26159.112/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.2.26159.112/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 11.0.100-preview.1.26104.118 You can build .NET 11.0 Preview 1 from the repository by cloning the release tag `v11.0.100-preview.1.26104.118` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.1.26104.118/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v11.0.100-preview.1.26104.118/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## 10.0.404 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.404` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.404/README.md#building). Alternatively, you can build from the sources attached to this release directly. More information on this process can be found in the [dotnet/dotnet repository](https://github.com/dotnet/dotnet/blob/v10.0.404/README.md#building-from-released-sources). Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023 ## Important Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.404-servicing.26529.119.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID `2001:2001`, while GitHub’s automatically generated archives use `0:0`. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail. Commits viewable in [compare view](dotnet/dotnet@v10.0.403...v11.0.100). </details> Updated [ptr727.Utilities](https://github.com/ptr727/Utilities) from 4.1.109 to 4.1.112. <details> <summary>Release notes</summary> _Sourced from [ptr727.Utilities's releases](https://github.com/ptr727/Utilities/releases)._ ## 4.1.112 ## What's Changed * Bump the actions-deps group with 4 updates by @dependabot[bot] in ptr727/Utilities#586 * Bump the nuget-deps group with 1 update by @dependabot[bot] in ptr727/Utilities#588 **Full Changelog**: ptr727/Utilities@4.1.109...4.1.112 Commits viewable in [compare view](ptr727/Utilities@4.1.109...4.1.112). </details> Updated [System.CommandLine](https://github.com/dotnet/dotnet) from 2.0.14 to 3.0.0. <details> <summary>Release notes</summary> _Sourced from [System.CommandLine's releases](https://github.com/dotnet/dotnet/releases)._ No release notes found for this version range. Commits viewable in [compare view](https://github.com/dotnet/dotnet/commits). </details> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
) ## Summary Resyncs the carried instruction set and the `.github/skills` tree to hub `009d3e5e`, RESYNC.md steps 1 and 3 in one pull request per RESYNC.md section 6. Measured by `audit run 2026-11-12T22:10:34Z | hub 009d3e5e` against `main`: 8 verbatim-section drifts, 7 intent staleness advisories, 1 letter and 29 drifts in the skills tree. - **Verbatim sections.** `carry.py apply-sections` re-vendored `AGENTS.md` "Where the Rules Live" and seven `GOVERNANCE.md` sections. Every region was stale (matched a past hub revision), so no local text was in them. The preamble and "Repository Layout" came through byte-identical. - **Intent files.** `CODESTYLE.md` and `WORKFLOW.md` each matched a past hub revision byte for byte, so the `carried-instruction-file-guard` probe found no local addition, and each takes the current hub text. - **`AUDIT.md`.** It is replaced by the short, repository-scoped form that hub `STANDUP.md` and the `standup-a-repo` skill now require (hub #3920), the shape PhotoCleaner and DevKitCIoT carry. The near-whole copy it replaces is what kept drifting. - **`.github/copilot-instructions.md`.** It takes the current hub text and keeps this repository's own "Disproved Claims" ledger sentence. Its only skill path, `fleet-code-review`, is unchanged. - **Skills tree.** `carry.py apply` refreshes 27 stale files and adds `update-host`, which `AGENTS.md` "Where the Rules Live" now names. ## Follow-Up, After This Merges RESYNC.md step 6 intent files land in their own pull request, branched from `develop` once this one merges: - `global.json` gains the `sdk` block (`10.0.100`, `latestFeature`, `allowPrerelease: false`) that the carried `CODESTYLE.md` and `dotnet-codestyle` skill now require. Until then the repo's `global.json` trails that rule. The local strict review raised this as `introduced`, and it is handed to that pull request rather than fixed here, per the RESYNC.md apply order. - `cspell.json` drops `gruntfuggly`, which the hub removed with its extension and nothing here uses. - `version.json` needs nothing. Its advisory traces to a wording-only hub edit to `WORKFLOW.md`. ## Verification - `carry.py check-sections` and `carry.py check` report no remaining stale, missing, or extra paths after apply. - `prose_lint.py --diff` against the merge base is clean (34 files, 670 changed lines). - Local strict review passes are recorded at each content state; the last covers this head. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
## Summary RESYNC.md section 3 step 4, the interface workflows, after the instruction-set pull request #501. It brings the four caller workflows and the validate composite action level with hub release 2.0.1421 (`009d3e5e`) and the current catalog stubs. Measured by `audit run 2026-11-12T22:10:34Z | hub 009d3e5e` and a hand comparison against `catalog/snippets/workflows/`, which the audit does not mechanize (hub #4117). - **Pins.** Every `ptr727/ProjectTemplate/.github/workflows/*-task.yml` pin moves from 2.0.1401 to 2.0.1421. The hub's `.github/workflows` and `.github/actions` are unchanged between the two, so no input, secret, or output moves. - **Merge-bot.** It adds `closed` to the trigger and `with: delete-branch: true`. `docs/reusable-workflows.md` already records LanguageTags as a `delete-branch: true` adopter, and `delete_branch_on_merge` is off fleet-wide, so bot head branches piled up. The task deletes only a merged, in-repo bot head (hub #2336). - **Test pull request.** The `pull_request` trigger drops its base filter, so a stacked pull request runs, per `docs/reusable-workflows.md`. The aggregator requires `success` from `changes` and `validate` and allows `skipped` only for `smoke-build`, as the smoke stub does. Neither job can skip on any trigger here. - **Publish.** The artifact delete is gated on the download succeeding, per D5.2, and reads the run and ref from the environment as the stub does. The recovery comment now names the routes D4.5 leaves once the delete runs after a failed push. - **Validate action.** `actions/setup-dotnet` moves from v6.0.0 to v6.1.0, the SHA `publish-release.yml` already pins. `global.json` joins both path lists in the step-6 pull request that gives it the `sdk` block, since until then it does not affect the shipped package. ## Verification - actionlint is clean through the hub's `scripts/docker_lint.py`. - `prose_lint.py --allow-comments --diff` against the merge base is clean. The pull request carries the `comments` label for the workflow comments it changes. - Local strict review passes are recorded at each content state, and the last one covers this head. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
## Summary RESYNC.md section 3 step 6, the intent and repo-owned files, after the instruction set (#501) and the caller workflows (#502). With this, LanguageTags is level with hub release 2.0.1421 (`009d3e5e`) on the surfaces the audit measures and on the ones it does not (hub #4117). NxWitness #686 and #688 are the precedent. - **`global.json`** selects the .NET 10 SDK line (`10.0.100`, `rollForward` `latestFeature`, `allowPrerelease` `false`), per the carried `dotnet-codestyle` rule. It keeps the Microsoft.Testing.Platform runner key. The publisher's push paths and the smoke filter now list it, as the hub stubs do and D6.4 requires of the two lists together. - **`hub_fetch_run.py`** is the hub's `catalog/snippets/hub_fetch_run.py`, copied verbatim to the repo root. - **`.husky/pre-commit`** is the husky snippet minus its Python block. The .NET half runs unguarded, and the prose gate (staged paths) and EOL check run through the helper. The repo's own guarded `husky.sh` source stays. No per-file LF pin is added, per `recurring.eol` (hub #4121). - **`.vscode/tasks.json`** takes the snippet's Lint group. The four Docker linters go through `scripts/docker_lint.py`, and `Lint: Prose` and `Lint: EOL` are added. - **`.github/dependabot.yml`** takes the snippet's `exclude-patterns` for the dotnet tools and watches `/.github/actions/*` for action pins. - **`ManagePackageVersionsCentrally`** moves to `Directory.Packages.props`, per `dotnet-codestyle`. - **`LanguageTags.code-workspace`** gains the base fragment's `markdown.extension.toc.levels` and `git.alwaysSignOff`. The README TOC drops its H1 entry to match `2..3`. - **`cspell.json`** drops `gruntfuggly`, which the hub removed and nothing here uses. - **`OPERATIONS.md`** and **`host-tools.json`** describe the hook halves, the Lint tasks, the helper, and the SDK selection. ## Verification On a host carrying a newer SDK major beside the 10.0 line, `dotnet` now selects the 10.0 SDK, where it picked the newer major before. - `dotnet build`: 0 warnings, 0 errors. - `dotnet format style --verify-no-changes --severity=info`: clean. - `dotnet test`: every test passed. - `host-tools.json` now says the host gate cannot see a missing 10.0 line, a gap added to hub #4106. - editorconfig-checker, markdownlint, cspell, shellcheck, shfmt, and actionlint are clean through the hub's `scripts/docker_lint.py`. - Both commits went through the new pre-commit hook, its prose and EOL gates included, with no `HUSKY=0`. - Local strict review passes are recorded at each content state, and the last one covers this head. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #504 +/- ##
=======================================
Coverage 87.68% 87.68%
=======================================
Files 11 11
Lines 1941 1941
Branches 252 252
=======================================
Hits 1702 1702
Misses 166 166
Partials 73 73 🚀 New features to boost your workflow:
|
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Approval is blocked by an unvalidated hub path that can overwrite files outside the scratch directory, along with missing signal handling and child cleanup in both the hook and runner.
3 open issues
What changed in this PR
This pull request promotes develop to main and resynchronizes LanguageTags with hub release 2.0.1421 across repository guidance, .NET tooling, local gates, and GitHub Actions workflows.
Changes:
- Resynchronizes fleet instructions, Skills, governance references, and operations documentation.
- Selects the .NET 10 SDK line, enables central package management, and updates tool and dependency versions.
- Refreshes workflow pins and publishing behavior, including broader pull request validation, artifact cleanup, and bot branch deletion.
- Adds the hub script loader and updates local lint and pre-commit integration.
| File | Description |
|---|---|
| README.md | Updates the generated table of contents for heading levels 2 through 3. |
| OPERATIONS.md | Documents hub-fetched local gates, lint tasks, and centralized configuration. |
| LanguageTags.code-workspace | Adds Markdown TOC levels and Git sign-off settings. |
| hub_fetch_run.py | Adds the hub script loader used by local gates. |
| host-tools.json | Documents the .NET 10 SDK-line requirement and host limitation. |
| GOVERNANCE.md | Resynchronizes governance rules for decisions, observed data, tooling, reviews, and configuration. |
| global.json | Selects the .NET 10 SDK line and Microsoft Testing Platform runner. |
| Directory.Packages.props | Enables central package management and updates package versions. |
| Directory.Build.props | Removes the package-management property moved to Directory.Packages.props. |
| cspell.json | Removes an obsolete accepted spelling. |
| CODESTYLE.md | Adds interrupt-handling rules and documents SDK-line configuration. |
| AGENTS.md | Updates routing for short names and the new host-update Skill. |
| .vscode/tasks.json | Routes lint tasks through hub tooling and adds prose and EOL tasks. |
| .husky/pre-commit | Adds staged prose and repository EOL gates. |
| .github/workflows/test-pull-request.yml | Validates all pull requests, includes global.json, and updates aggregation behavior. |
| .github/workflows/run-periodic-codegen-pull-request.yml | Updates the reusable codegen workflow pin. |
| .github/workflows/publish-release.yml | Updates release pins, SDK-sensitive paths, recovery guidance, and artifact cleanup. |
| .github/workflows/merge-bot-pull-request.yml | Adds closed-event handling and enables merged bot branch deletion. |
| .github/skills/workflow-ci-contract/references/test-methodology.md | Updates workflow trace scenarios and configuration references. |
| .github/skills/workflow-ci-contract/references/d-guarantees.md | Updates workflow guarantees for pull request triggers, coverage, and publishing. |
| .github/skills/workflow-ci-contract/references/architecture.md | Documents unfiltered pull request validation. |
| .github/skills/update-host/SKILL.md | Adds the combined host setup and status procedure. |
| .github/skills/standup-a-repo/SKILL.md | Updates standup sequencing and branch-level resynchronization guidance. |
| .github/skills/shell-codestyle/SKILL.md | Adds shell interrupt guidance. |
| .github/skills/session-handoff/SKILL.md | Updates handoff parsing, decision parking, and cleanup rules. |
| .github/skills/resync-a-repo/SKILL.md | Updates resynchronization ordering and grouping rules. |
| .github/skills/repo-worktree/SKILL.md | Documents ignored-file handling during cleanup. |
| .github/skills/python-codestyle/SKILL.md | Adds Python interrupt guidance. |
| .github/skills/pr-review-conduct/SKILL.md | Updates promotion coverage and observed-data outcomes. |
| .github/skills/merge-and-release/SKILL.md | Extends hub release refreshes to the host safety kit. |
| .github/skills/local-strict-review/SKILL.md | Updates review-round handling for observed data. |
| .github/skills/git-commit-conventions/SKILL.md | Adds target-repository identity and signing checks. |
| .github/skills/fleet-code-review/SKILL.md | Removes the obsolete machine-readable review marker requirement. |
| .github/skills/drive-pr/SKILL.md | Carries updated observed-data review outcomes. |
| .github/skills/dotnet-codestyle/SKILL.md | Documents the required SDK line and global.json configuration. |
| .github/skills/dotnet-codestyle/references/testing.md | Connects the Microsoft Testing Platform runner requirement to SDK configuration. |
| .github/skills/dotnet-codestyle/references/project-config.md | Documents the .NET 10 SDK and target framework relationship. |
| .github/skills/decision-triage/SKILL.md | Updates deferred-decision rechecks and reporting. |
| .github/skills/copilot-instructions-keeper/SKILL.md | Simplifies current-content comparison guidance. |
| .github/skills/comment-and-doc-style/SKILL.md | Resynchronizes Markdown, prose, and spelling rules. |
| .github/skills/comment-and-doc-style/references/line-endings.md | Updates tool-owned and byte-preserved file guidance. |
| .github/skills/check-this-repo/SKILL.md | Points stale host-state checks to the combined host setup. |
| .github/skills/branching-and-release-model/references/branch-protection-and-promotion.md | Updates ruleset application ordering and branch selection. |
| .github/skills/backlog-burndown/SKILL.md | Adds net-flow reporting and deferred-issue handling. |
| .github/skills/audit-a-repo/SKILL.md | Updates audit branch selection, report naming, and manual findings guidance. |
| .github/skills/agent-conduct/SKILL.md | Updates handoff decision blocking rules. |
| .github/dependabot.yml | Excludes tool packages and adds composite-action directories. |
| .github/copilot-instructions.md | Removes the obsolete review marker requirement and updates coverage guidance. |
| .github/actions/validate/action.yml | Updates actions/setup-dotnet to v6.1.0. |
| .config/dotnet-tools.json | Updates CSharpier to version 1.4.0. |
Review effort: Lite
Owner
Author
|
Merge Gate item 2, promotion case, for head
Every thread on this promotion is resolved, all 23 checks pass, and |
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Promotes
developtomain. It carries the fourth resync of LanguageTags against hub release 2.0.1421 (009d3e5e), which brings the repository level with the fleet on the surfaces the audit measures and on the ones it does not.maintook in #499).github/skillstree, and the short, repository-scopedAUDIT.mdclosed+delete-branch, unfilteredpull_request, success-only aggregator, D5.2 artifact delete, setup-dotnet v6.1.0global.jsonSDK line,hub_fetch_run.py, the hub pre-commit doc gates, the VS Code Lint group, Dependabot tool exclusions and the actions glob, CPM inDirectory.Packages.props, workspace settings, OPERATIONS.md and host-tools.jsonaudit run 2026-11-12T23:11:04Z | hub 009d3e5e | branch override developreports 0 defect, letter, or error findings. Two advisories remain:Directory.Packages.propschanged on both branches.developcarries the same five version bumpsmaintook in Bump the nuget-deps group with 6 updates #499, plus the CPM property, so it supersedesmainthere, andgit merge-treeof the two is clean.version.jsontrails aWORKFLOW.mdD3 edit by date. That edit was wording-only, so there is nothing to change.Repository settings, rulesets, and secrets were reconciled by
repo-config/configure.sh applyfrom hubmain, andcheckreports a match.Hub Issues Filed or Updated
#4115, #4117, #4118, #4121, and #4122 were filed. #2336 and #4106 were commented on.
This is a merge-commit promotion. A human merge publishes nothing, so a release is a separate dispatch.
🤖 Generated with Claude Code