allow checking formatting with cache#1830
Merged
Merged
Conversation
Author
|
I think there's probably nothing to test here; it doesn't look like there were tests for the previous behaviour (and no tests for the CLI arguments in general as far as I can tell) |
belav
requested changes
Mar 15, 2026
belav
left a comment
belav
left a comment
Owner
There was a problem hiding this comment.
My worry with this change is that I had a commit to specifically disable the cache when running check, but I don't recall why I would have made that change and neglected to leave a comment explaining why.
It seems safer to have a new option for the check command --use-cache so that it can default to the current behavior.
Author
|
I do think it's a little unfortunate to have a different API surface between checking and formatting but I made that change |
belav
approved these changes
Mar 22, 2026
belav
left a comment
belav
left a comment
Owner
There was a problem hiding this comment.
Thanks for updating. I was thinking that running the check command in a GH action may have had issues with using the cache. That might be why I disabled it for the check command.
Author
|
Thanks! I'm planning to try it out in CI so I'll report back if there are any issues. |
This was referenced Jun 7, 2026
ptr727-codegen Bot
pushed a commit
to ptr727/LanguageTags
that referenced
this pull request
Jun 8, 2026
Updated [csharpier](https://github.com/belav/csharpier) from 1.2.6 to 1.3.0. <details> <summary>Release notes</summary> _Sourced from [csharpier's releases](https://github.com/belav/csharpier/releases)._ ## 1.3.0 # 1.3.0 ## Breaking Changes ### Change xml formatting to return error when it runs into syntax error so it is consistent with c# [#1854](belav/csharpier#1854) Previously CSharpier treated an invalid xml file as a warning instead of an error. This was inconsistent with how it treated c# files. Invalid c# or xml files are not treated as errors. The `--compilation-errors-as-warnings` argument has been renamed to `--syntax-errors-as-warnings` and can be used to return warnings instead of errors when encountering invalid files. ## What's Changed ### Feature: Configurable whitespace handling for xml [#1790](belav/csharpier#1790) CSharpier now supports two types of xml whitespace formatting strict or ignore. By default all xml except `xaml` or `axaml` is treated as strict whitespace. See [details](https://csharpier.com/docs/Configuration#xml-whitespace-sensitivity) ### Feature: Move closing bracket for xml elements to the same line. [#1598](belav/csharpier#1598) With strict xml whitespace handling, csharpier now keeps the closing bracket for an element on the same line instead of breaking it to a new line. ```xml <!-- input & expected output --> <ElementWithAttribute Attribute="AttributeValue__________________" >TextValue</ElementWithAttribute> <!-- 1.2.6 --> <ElementWithAttribute Attribute="AttributeValue__________________" >TextValue</ElementWithAttribute > ``` ### Feature: Support for csharpier-ignore with XML formatter [#1788](belav/csharpier#1788) CSharpier now supports `csharpier-ignore` in xml files. See [details](https://csharpier.com/docs/Ignore#xml) ### Feature: Add MSBuild transitive and multi-target support [#1833](belav/csharpier#1833) CSharpier.MSBuild can now work as a transitive dependency. ### Feature: allow checking formatting with cache [#1830](belav/csharpier#1830) The `csharpier check` command now supports a `--use-cache` option. ### Feature: remove dependency on Microsoft.AspNetCore.App [#1508](belav/csharpier#1508) Previously CSharpier required that Microsoft.AspNetCore.App be installed. CSharpier has been modified to use an HttpListener when it is run using `server` to remove the need for this dependency. ### Fix: csharpier-ignore comment removes linespaces before block [#1867](belav/csharpier#1867) CSharpier was removing blank lines before csharpier-ignore comments in some cases ```c# // input and expected output var x = 1; // csharpier-ignore var y=1; /// 1.2.6 var x = 1; // csharpier-ignore var y=1; ... (truncated) Commits viewable in [compare view](belav/csharpier@1.2.6...1.3.0). </details> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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>
This was referenced Jul 2, 2026
Merged
jordanstarksbrowning-hippo
added a commit
to DFE-Digital/single-unique-identifier
that referenced
this pull request
Jul 7, 2026
Pinned [Azure.Identity](https://github.com/Azure/azure-sdk-for-net) at
1.21.0.
<details>
<summary>Release notes</summary>
_Sourced from [Azure.Identity's
releases](https://github.com/Azure/azure-sdk-for-net/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/Azure/azure-sdk-for-net/commits).
</details>
Updated
[Azure.Monitor.OpenTelemetry.Exporter](https://github.com/Azure/azure-sdk-for-net)
from 1.6.0 to 1.8.2.
<details>
<summary>Release notes</summary>
_Sourced from [Azure.Monitor.OpenTelemetry.Exporter's
releases](https://github.com/Azure/azure-sdk-for-net/releases)._
## 1.8.2
## 1.8.2 (2026-06-30)
### Features Added
- Added support for the Microsoft OpenTelemetry distro's SDK statistics:
a new internal meter subscription and an AppContext switch
(`Azure.Monitor.OpenTelemetry.Exporter.RouteSdkStatsToDistroEndpoint`)
that lets the distro redirect SDK statistics to its own ingestion path.
The ingestion destination and an on/off signal are resolved at startup
by fetching a remote configuration; on success the configured
destination is used, an explicit remote disable signal turns SDK
statistics off, and any other outcome falls back to the existing
region-derived ingestion endpoint so SDK statistics keep flowing. The
AppContext switch has no effect on Statsbeat for callers that do not opt
in.
([#59811](https://github.com/Azure/azure-sdk-for-net/pull/59811))
- Subscribed the Statsbeat `MeterProvider` to the Microsoft
OpenTelemetry distro's Network SDKStats meter
(`MicrosoftOpenTelemetryNetworkSdkStatsMeter`) so distro-emitted Network
statistics flow through the existing Statsbeat cadence when the distro
runs with a non-Azure-Monitor exporter.
([#60209](https://github.com/Azure/azure-sdk-for-net/pull/60209))
- Subscribed the Statsbeat `MeterProvider` to the Microsoft
OpenTelemetry distro's Feature SDKStats meter
(`MicrosoftOpenTelemetryFeatureSdkStatsMeter`) so distro-emitted Feature
statistics reach the Statsbeat ingestion path. The distro uses an
independent, spec-aligned bit map to avoid collisions with the classic
Application Insights SDK's `FeatureStatsbeatMeter`.
([#59529](https://github.com/Azure/azure-sdk-for-net/pull/59529))
- Added Network SDKStats reporting, emitting the short-interval Network
statistics defined in the Application Insights SDKStats spec on a
15-minute cadence: `Request_Success_Count`, `Request_Failure_Count`,
`Request_Duration`, `Retry_Count`, `Throttle_Count`, and
`Exception_Count`, each with the spec-defined dimensions (including
`host`, `statusCode`, and `exceptionType`).
([#59909](https://github.com/Azure/azure-sdk-for-net/pull/59909),
[#60018](https://github.com/Azure/azure-sdk-for-net/pull/60018))
### Other Changes
- Updated customer SDK stats dimension key names to use camelCase
(`computeType`, `telemetryType`, `dropCode`, `dropReason`, `retryCode`,
`retryReason`).
([#59902](https://github.com/Azure/azure-sdk-for-net/pull/59902))
Commits viewable in [compare
view](https://github.com/Azure/azure-sdk-for-net/commits/Azure.Monitor.OpenTelemetry.Exporter_1.8.2).
</details>
Updated
[coverlet.collector](https://github.com/coverlet-coverage/coverlet) from
8.0.1 to 10.0.1.
<details>
<summary>Release notes</summary>
_Sourced from [coverlet.collector's
releases](https://github.com/coverlet-coverage/coverlet/releases)._
## 10.0.1
### Improvements
- Coverlet with MTP 2 doesn't show test coverage statistic in console
[#1907](https://github.com/coverlet-coverage/coverlet/issues/1907)
- Avoid unnecessary testhost restarts
[#1912](https://github.com/coverlet-coverage/coverlet/issues/1912) by
<https://github.com/mawosoft>
### Fixed
- Fix inconsistent paths in cobertura reports
[#1723](https://github.com/coverlet-coverage/coverlet/issues/1723)
- Fix when using "is" with "and" in pattern matching, branch coverage is
lower than normal
[#1313](https://github.com/coverlet-coverage/coverlet/issues/1313)
- Fix Coverlet flagging a branch for an async functions finally block
where none exists
[#1337](https://github.com/coverlet-coverage/coverlet/issues/1337)
- Fix Coverlet Tracker Missing CompilerGeneratedAttribute
[#1828](https://github.com/coverlet-coverage/coverlet/issues/1828)
### Maintenance
- Add architecture docs and diagrams for all integrations
[#1927](https://github.com/coverlet-coverage/coverlet/pull/1927)
- Update NuGet packages and .NET SDK versions
[#1933](https://github.com/coverlet-coverage/coverlet/pull/1933)
[Diff between 10.0.0 and
10.0.1](https://github.com/coverlet-coverage/coverlet/compare/v10.0.0...v10.0.1)
## 10.0.0
## Improvements
- Unique Report Filenames (coverlet.MTP and AzDO)
[#1866](https://github.com/coverlet-coverage/coverlet/issues/1866)
- Add `--coverlet-file-prefix` option for unique report files
[#1869](https://github.com/coverlet-coverage/coverlet/pull/1869)
- Introduce .NET 10 support
[#1823](https://github.com/coverlet-coverage/coverlet/pull/1823)
## Fixed
- Fix [BUG] Wrong branch rate on IAsyncEnumerable for generic type
[#1836](https://github.com/coverlet-coverage/coverlet/issues/1836)
- Fix [BUG] Missing Coverage after moving to MTP
[#1843](https://github.com/coverlet-coverage/coverlet/issues/1843)
- Fix [BUG] No coverage reported when targeting .NET Framework with
8.0.1
[#1842](https://github.com/coverlet-coverage/coverlet/issues/1842)
- Fix [BUG] Behavior changes between MTP and Legacy (msbuild)
[#1878](https://github.com/coverlet-coverage/coverlet/issues/1878)
- Fix [BUG] Coverlet.MTP - Unable to load coverlet.mtp.appsettings.json
[#1880](https://github.com/coverlet-coverage/coverlet/issues/1880)
- Fix [BUG] Coverlet.Collector produces empty report when
Mediator.SourceGenerator is referenced
[#1718](https://github.com/coverlet-coverage/coverlet/issues/1718) by
<https://github.com/yusyd>
- Fix [BUG] Crash during instrumentation (Methods using
LibraryImport/DllImport have no body)
[#1762](https://github.com/coverlet-coverage/coverlet/issues/1762)
## Maintenance
- Add comprehensive async method tests and documentation for issue
[#1864](https://github.com/coverlet-coverage/coverlet/pull/1864)
- Replace Tmds.ExecFunction Package in coverlet.core.coverage.tests
[#1833](https://github.com/coverlet-coverage/coverlet/issues/1833)
- Add net9.0 and net10.0 targets
[#1822](https://github.com/coverlet-coverage/coverlet/issues/1822)
[Diff between 8.0.1 and
10.0.0](https://github.com/coverlet-coverage/coverlet/compare/v8.0.1...v10.0.0)
Commits viewable in [compare
view](https://github.com/coverlet-coverage/coverlet/compare/v8.0.1...v10.0.1).
</details>
Updated [csharpier](https://github.com/belav/csharpier) from 1.2.6 to
1.3.0.
<details>
<summary>Release notes</summary>
_Sourced from [csharpier's
releases](https://github.com/belav/csharpier/releases)._
## 1.3.0
# 1.3.0
## Breaking Changes
### Change xml formatting to return error when it runs into syntax error
so it is consistent with c#
[#1854](https://github.com/belav/csharpier/pull/1854)
Previously CSharpier treated an invalid xml file as a warning instead of
an error. This was inconsistent with how it treated c# files.
Invalid c# or xml files are not treated as errors.
The `--compilation-errors-as-warnings` argument has been renamed to
`--syntax-errors-as-warnings` and can be used to return warnings instead
of errors when encountering invalid files.
## What's Changed
### Feature: Configurable whitespace handling for xml
[#1790](https://github.com/belav/csharpier/issues/1790)
CSharpier now supports two types of xml whitespace formatting strict or
ignore.
By default all xml except `xaml` or `axaml` is treated as strict
whitespace. See
[details](https://csharpier.com/docs/Configuration#xml-whitespace-sensitivity)
### Feature: Move closing bracket for xml elements to the same line.
[#1598](https://github.com/belav/csharpier/issues/1598)
With strict xml whitespace handling, csharpier now keeps the closing
bracket for an element on the same line instead of breaking it to a new
line.
```xml
<!-- input & expected output -->
<ElementWithAttribute Attribute="AttributeValue__________________"
>TextValue</ElementWithAttribute>
<!-- 1.2.6 -->
<ElementWithAttribute Attribute="AttributeValue__________________"
>TextValue</ElementWithAttribute
>
```
### Feature: Support for csharpier-ignore with XML formatter
[#1788](https://github.com/belav/csharpier/issues/1788)
CSharpier now supports `csharpier-ignore` in xml files. See
[details](https://csharpier.com/docs/Ignore#xml)
### Feature: Add MSBuild transitive and multi-target support
[#1833](https://github.com/belav/csharpier/issues/1833)
CSharpier.MSBuild can now work as a transitive dependency.
### Feature: allow checking formatting with cache
[#1830](https://github.com/belav/csharpier/pull/1830)
The `csharpier check` command now supports a `--use-cache` option.
### Feature: remove dependency on Microsoft.AspNetCore.App
[#1508](https://github.com/belav/csharpier/issues/1508)
Previously CSharpier required that Microsoft.AspNetCore.App be
installed. CSharpier has been modified to use an HttpListener when it is
run using `server` to remove the need for this dependency.
### Fix: csharpier-ignore comment removes linespaces before block
[#1867](https://github.com/belav/csharpier/issues/1867)
CSharpier was removing blank lines before csharpier-ignore comments in
some cases
```c#
// input and expected output
var x = 1;
// csharpier-ignore
var y=1;
/// 1.2.6
var x = 1;
// csharpier-ignore
var y=1;
... (truncated)
```
Commits viewable in [compare
view](https://github.com/belav/csharpier/compare/1.2.6...1.3.0).
</details>
Updated
[dotnet-reportgenerator-globaltool](https://github.com/danielpalme/ReportGenerator)
from 5.5.4 to 5.5.10.
<details>
<summary>Release notes</summary>
_Sourced from [dotnet-reportgenerator-globaltool's
releases](https://github.com/danielpalme/ReportGenerator/releases)._
## 5.5.10
# Changes:
- Added support for Sha256 signed licenses
This release requires .NET Framework 4.7 or .NET 8.0/9.0/10.0
## 5.5.9
# Changes:
- Added new setting "applyQueryStringToAllLinks" to apply query string
to referenced CSS and JavaScript files and links to support SAS tokens
(e.g. on blob storage) (#349)
- Improved escaping of JavaScript content
This release requires .NET Framework 4.7 or .NET 8.0/9.0/10.0
## 5.5.8
# Changes:
- Azure DevOps: Added metadata to become a trusted publisher
This release requires .NET Framework 4.7 or .NET 8.0/9.0/10.0
## 5.5.7
# Changes:
- #783: Reduce memory usage for large code files
This release requires .NET Framework 4.7 or .NET 8.0/9.0/10.0
## 5.5.6
# Changes:
-
https://github.com/danielpalme/ReportGenerator-GitHub-Action/issues/39:
Github Action: Allow runner.temp directory
This release requires .NET Framework 4.7 or .NET 8.0/9.0/10.0
## 5.5.5
# Changes:
- #780: Improved branch handling for Coberatura files (contributed by
@lorenz-ammersbach)
- #782: Dynamic metric rows (assemblies/modules) in HTML report
-
https://github.com/danielpalme/ReportGenerator-GitHub-Action/issues/37:
Github Action: Added input validation and path scope enforcement
(contributed by @ismits)
This release requires .NET Framework 4.7 or .NET 8.0/9.0/10.0
Commits viewable in [compare
view](https://github.com/danielpalme/ReportGenerator/compare/v5.5.4...v5.5.10).
</details>
Updated [DotNetEnv](https://github.com/tonerdo/dotnet-env) from 3.1.1 to
3.2.0.
<details>
<summary>Release notes</summary>
_Sourced from [DotNetEnv's
releases](https://github.com/tonerdo/dotnet-env/releases)._
## 3.2.0
- Switch parsing to Superpower (from Sprache)
- Fix utf8 parsing
- Interpolated variables parsing
Commits viewable in [compare
view](https://github.com/tonerdo/dotnet-env/compare/v3.1.1...v3.2.0).
</details>
Pinned [Hl7.Fhir.R4](https://github.com/FirelyTeam/firely-net-sdk) at
6.2.1.
<details>
<summary>Release notes</summary>
_Sourced from [Hl7.Fhir.R4's
releases](https://github.com/FirelyTeam/firely-net-sdk/releases)._
## 6.2.1
## Intro:
This is a bugfix release with several stability and correctness
improvements.
**Serialization**
- Fixed an `OverflowException` when serializing large decimal values
with old parsing stack
- Switched `FhirClient` to use the modern POCO serializer for better
consistency
- If legacy serializers are still needed, our choice can be overriden by
assigning `Settings.SerializationEngine` an instance of
`FhirSerializationEngineFactory.Legacy.FromParserSettings(ModelInfo.ModelInspector,
Settings.ParserSettings ?? new())` as it was before
- Fixed size limitations when serializing base64-encoded data
- Fixed the `pretty` option being ignored when calling `ToXml()`
**Snapshot generation**
- Fixed incorrect behavior in collection merge when suppression
extensions were involved, which could cause an index-out-of-range error
or suppression being silently ignored
**POCO / type system**
- `ISourceNode` now has a direct `ToPoco()` extension method
- Fixed `instant` values being stored incorrectly when converting from
an untyped source
- Untyped sources are now correctly associated with the model when
building POCOs
- Custom resources and datatypes are now easier to define and build as a
`ClassMapping` for `ModelInspector`
- Restored collection initializer syntax support on the `Parameters`
class
- Added `IVersionableConformanceResource` to R5 `NamingSystem`
**Other fixes**
- Resolver base class now allows returning `null`, leaving it to the
caller to decide whether to throw
- Dependencies downgraded to align with the target framework version
## Changes:
* #3535: Added more tests cases for unit tests. Some code cleanup.
* #3536: Pretty parameter is not being used in ToXml extension method.
* #3534: Fix: store 'instant' as canonical string when building a POCO
from an untyped source
* #3531: Fix serialization base64 size limits
* #3472: Add direct ISourceNode.ToPoco() implementation
* #3526: Fixed incorrect merge logic in mergeCollectionWithSuppression
that could result in suppression extension not being honoured
* #3530: Skip major version update rules for specific dependencies
* #3527: Bump the runtime-dependencies-minor group with 1 update
* #3509: Central Package Dependency Management AND LTS/Condition
Suggestions
* #3525: Optimize serialization locking
## 6.2.0
## Intro:
* Added a `RespectSuppressExtension` setting to
`SnapshotGeneratorSettings` (default: `true`) to allow consumers to opt
out of suppress-extension handling during snapshot generation.
* Added `Base.ClearOverflow()` and corrected the `NoOverflow` docstring.
* `ITypedElement` extension methods now use
`OverloadResolutionPriority(1)`, ensuring they are preferred over
`ISourceNode` extensions for types implementing both interfaces (such as
`PocoNode`).
* Fixed a cache key issue in `CachingTerminologyService` where resource
or unrecognized parameter values could produce invalid cache keys.
* Validation now includes canonicals in failed resolve attempts, and
cardinality validation correctly handles cases where no member name is
reported.
* Updated `System.Text.Json` and `Microsoft.Extensions.Caching.Memory`
to version `10.0.7`.
## Changes:
* #3492: Bump Microsoft.Extensions.Caching.Memory and 4 others
* #3496: Skip build stages when only docs change (DEVOPS-706,
DEVOPS-709)
* #3491: Added RespectSuppressExtension to SnapshotGeneratorSettings
* #3490: Fix small bug in the CachingTerminologyService
* #3487: Bump the test-dependencies group with 1 update
* #3483: Bump the runtime-dependencies-minor group with 4 updates
* #3479: Add ClearOverflow() to Base and fix misleading NoOverflow
docstring
* #3475: Handle the case of cardinality validation not reporting
membername
* #3470: Include canonicals in failed resolve attempts
* #3477: Add OverloadResolutionPriority to ITypedElement extensions
Commits viewable in [compare
view](https://github.com/FirelyTeam/firely-net-sdk/compare/v6.1.1...v6.2.1).
</details>
Updated
[Microsoft.Azure.Functions.Worker](https://github.com/Azure/azure-functions-dotnet-worker)
from 2.51.0 to 2.52.0.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Azure.Functions.Worker's
releases](https://github.com/Azure/azure-functions-dotnet-worker/releases)._
## 2.52.0
## What's Changed
### Microsoft.Azure.Functions.Worker (metapackage) 2.52.0
- Update `Microsoft.Azure.Functions.Worker.Core` to 2.52.0
- Update `Microsoft.Azure.Functions.Worker.Grpc` to 2.52.0
### Microsoft.Azure.Functions.Worker.Core 2.52.0
- Add support for propagating trace context tags from worker to host
(#3303)
- Add support for propagating OpenTelemetry Baggage to the worker.
Requires use with the OpenTelemetry Extension to work end to end
(#3319).
### Microsoft.Azure.Functions.Worker.Grpc 2.52.0
- Update protobuf version to v1.12.0-protofile and add support for
propagating tags from the worker to the functions host (#3303).
- Update protobuf version to v1.13.0-protofile to add support for
propagating OpenTelemetry baggage to the worker (#3319).
Commits viewable in [compare
view](https://github.com/Azure/azure-functions-dotnet-worker/compare/2.51.0...2.52.0).
</details>
Updated
[Microsoft.Azure.Functions.Worker.OpenTelemetry](https://github.com/Azure/azure-functions-dotnet-worker)
from 1.1.0 to 1.2.0.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Azure.Functions.Worker.OpenTelemetry's
releases](https://github.com/Azure/azure-functions-dotnet-worker/releases)._
## 1.2.0
## What's Changed
### Microsoft.Azure.Functions.Worker.OpenTelemetry 1.2.0
- Add support for propagating OpenTelemetry baggage to the worker
(#3319).
- `FunctionsResourceDetector` now respects `OTEL_SERVICE_NAME` and
`OTEL_RESOURCE_ATTRIBUTES` — when either is set, the detector skips
adding `service.name` and/or `service.version` so the OTel SDK picks
them up without duplication (#3362).
Commits viewable in [compare
view](https://github.com/Azure/azure-functions-dotnet-worker/commits/otel-1.2.0).
</details>
Pinned
[Microsoft.Extensions.Configuration.EnvironmentVariables](https://github.com/dotnet/dotnet)
at 10.0.9.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Extensions.Configuration.EnvironmentVariables's
releases](https://github.com/dotnet/dotnet/releases)._
## 10.0.0-preview.6.25358.103
You can build .NET 10.0 Preview 6 from the repository by cloning the
release tag `v10.0.0-preview.6.25358.103` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v10.0.0-preview.6.25358.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.0-preview.6.25358.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
## 10.0.0-preview.5.25277.114
You can build .NET 10.0 Preview 5 from the repository by cloning the
release tag `v10.0.0-preview.5.25277.114` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v10.0.0-preview.5.25277.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.0-preview.5.25277.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
## 10.0.0-preview.4.25258.110
You can build .NET 10.0 Preview 4 from the repository by cloning the
release tag `v10.0.0-preview.4.25258.110` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v10.0.0-preview.4.25258.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.0-preview.4.25258.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.0-preview.3.25171.5
You can build .NET 10.0 Preview 3 from the repository by cloning the
release tag `v10.0.0-preview.3.25171.5` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v10.0.0-preview.3.25171.5/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.0-preview.3.25171.5/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.0-preview.2.25163.2
You can build .NET 10.0 Preview 2 from the repository by cloning the
release tag `v10.0.0-preview.2.25163.2` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v10.0.0-preview.2.25163.2/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.0-preview.2.25163.2/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.0-preview.1.25080.5
You can build .NET 10.0 Preview 1 from the repository by cloning the
release tag `v10.0.0-preview.1.25080.5` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v10.0.0-preview.1.25080.5/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.0-preview.1.25080.5/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
## 9.0.118
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.118` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.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/v9.0.118/README.md#building-from-released-sources).
Attached is a PGP signature for the GitHub generated tarball. You can
find the public key at https://dot.net/release-key-2023
## 9.0.117
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.117` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.117/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/v9.0.117/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
## 9.0.116
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.116` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.116/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/v9.0.116/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
## 9.0.115
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.115` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.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/v9.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
## 9.0.114
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.114` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.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/v9.0.114/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
## 9.0.113
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.113` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.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/v9.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
## 9.0.112
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.112` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.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/v9.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
## 9.0.111
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.111` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.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/v9.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
## 9.0.110
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.110` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.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/v9.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
## 9.0.109
<!-- 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 9.0 from the repository by cloning the release tag
`v9.0.109` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.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/v9.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
## 9.0.101
You can build .NET 9.0 from the repository by cloning the release tag
`v9.0.101` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.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/v9.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
## 9.0.7
You can build .NET 9.0 from the repository by cloning the release tag
`v9.0.7` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.7/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/v9.0.7/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
## 9.0.6
You can build .NET 9.0 from the repository by cloning the release tag
`v9.0.6` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.6/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/v9.0.6/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
## 9.0.5
You can build .NET 9.0 from the repository by cloning the release tag
`v9.0.5` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.5/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/v9.0.5/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
## 9.0.4
You can build .NET 9.0 from the repository by cloning the release tag
`v9.0.4` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.4/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/v9.0.4/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
## 9.0.3
You can build .NET 9.0 from the repository by cloning the release tag
`v9.0.3` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.3/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/v9.0.3/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
## 9.0.2
You can build .NET 9.0 from the repository by cloning the release tag
`v9.0.2` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.2/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/v9.0.2/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
## 9.0.1
You can build .NET 9.0 from the repository by cloning the release tag
`v9.0.1` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.1/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/v9.0.1/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
## 9.0.0
You can build .NET 9.0 from the repository by cloning the release tag
`v9.0.0` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0/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/v9.0.0/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
## 9.0.0-rc.2.24473.5
You can build NET 9.0 RC2 from the repository by cloning the release tag
`v9.0.0-rc.2.24473.5` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0-rc.2.24473.5/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/v9.0.0-rc.2.24473.5/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
## 9.0.0-rc.1.24431.7
You can build .NET 9.0 RC1 from the repository by cloning the release
tag `v9.0.0-rc.1.24431.7` and following the build instructions in the
[main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0-rc.1.24431.7/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/v9.0.0-rc.1.24431.7/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
## 9.0.0-preview.7.24405.7
You can build .NET 9.0 Preview 7 from the repository by cloning the
release tag `v9.0.0-preview.7.24405.7` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0-preview.7.24405.7/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/v9.0.0-preview.7.24405.7/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
## 9.0.0-preview.6.24327.7
You can build .NET 9.0 Preview 6 from the repository by cloning the
release tag `v9.0.0-preview.6.24327.7` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0-preview.6.24327.7/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/v9.0.0-preview.6.24327.7/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
## 9.0.0-preview.5.24306.7
You can build .NET 9.0 Preview 5 from the repository by cloning the
release tag `v9.0.0-preview.5.24306.7` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0-preview.5.24306.7/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/v9.0.0-preview.5.24306.7/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
## 9.0.0-preview.4.24266.19
You can build .NET 9.0 Preview 4 from the repository by cloning the
release tag `v9.0.0-preview.4.24266.19` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0-preview.4.24266.19/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/v9.0.0-preview.4.24266.19/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
## 9.0.0-preview.3.24172.9
You can build .NET 9.0 Preview 3 from the repository by cloning the
release tag `v9.0.0-preview.3.24172.9` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0-preview.3.24172.9/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/v9.0.0-preview.3.24172.9/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
## 9.0.0-preview.2.24128.5
You can build .NET 9.0 Preview 2 from the repository by cloning the
release tag `v9.0.0-preview.2.24128.5` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0-preview.2.24128.5/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/v9.0.0-preview.2.24128.5/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
## 9.0.0-preview.1.24080.9
You can build .NET 9.0 Preview 1 from the repository by cloning the
release tag `v9.0.0-preview.1.24080.9` and following the build
instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v9.0.0-preview.1.24080.9/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/v9.0.0-preview.1.24080.9/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
## 8.0.128
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.128` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.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/v8.0.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
## 8.0.127
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.127` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.127/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/v8.0.127/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
## 8.0.126
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.126` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.126/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/v8.0.126/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
## 8.0.125
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.125` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.125/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/v8.0.125/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
## 8.0.124
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.124` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.124/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/v8.0.124/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
## 8.0.123
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.123` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.123/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/v8.0.123/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
## 8.0.122
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.122` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.122/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/v8.0.122/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
## 8.0.121
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.121` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.121/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/v8.0.121/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
## 8.0.120
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.120` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.120/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/v8.0.120/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
## 8.0.119
<!-- 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 8.0 from the repository by cloning the release tag
`v8.0.119` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.119/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/v8.0.119/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
## 8.0.100-preview.1
## 8.0.18
You can build .NET 8.0 from the repository by cloning the release tag
`v8.0.18` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.18/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/v8.0.18/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
## 8.0.17
You can build .NET 8.0 from the repository by cloning the release tag
`v8.0.17` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.17/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/v8.0.17/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
## 8.0.16
You can build .NET 8.0 from the repository by cloning the release tag
`v8.0.16` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.16/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/v8.0.16/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
## 8.0.15
You can build .NET 8.0 from the repository by cloning the release tag
`v8.0.15` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.15/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/v8.0.15/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
## 8.0.14
You can build .NET 8.0 from the repository by cloning the release tag
`v8.0.14` and following the build instructions in the [main
README.md](https://github.com/dotnet/dotnet/blob/v8.0.14/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/v8.0.14/README.md#building-from-released-sources).
Attached are PGP signatures for the GitHub genera...
_Description has been truncated_
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: jordanstarks-browning <jordan.starks-browning@hippodigital.co.uk>
This was referenced Jul 7, 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
2 participants
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.
Description
I run csharpier check as part of my lint flow, which means I run it a lot. On one of my repositories it takes 200ms to run format and 8000ms to run check. This PR allows for
checkto use the cache (although it can be disabled, just like forformat)Related Issue
Checklist
varthis.