[release-notes] .NET 11 Preview 5

.github/linters/.gitleaks.toml

@@ -0,0 +1,26 @@
+# Gitleaks configuration for super-linter.
+#
+# Super-linter v7 looks for gitleaks rules at .github/linters/.gitleaks.toml
+# (the same location as the other linter rule files in this directory).
+#
+# [extend] useDefault = true preserves the upstream gitleaks default rule set
+# (otherwise specifying a custom config silently disables every built-in rule).
+# We only add an allowlist for the auto-generated release-notes data files
+# whose VMR commit-SHA contents trigger false positives.
+#
+# Specifically, release-notes/**/changes.json contains thousands of 40-char
+# hex Git commit SHAs. SHAs that happen to start with "eaaa..." match the
+# square-access-token rule (which scans for EAAA[A-Za-z0-9_-]{60+}). The
+# files are tool-generated, not authored, so allowlisting them by path is
+# the right scope.
+
+[extend]
+useDefault = true
+
+[allowlist]
+description = "Release-notes skill generated data files"
+paths = [
+  '''release-notes/.+/changes\.json''',
+  '''release-notes/.+/features\.json''',
+  '''release-notes/.+/build-metadata\.json''',
+]

.github/skills/release-notes/references/editorial-rules.md

@@ -93,7 +93,7 @@ Thank you [@username](https://github.com/username) for this contribution!
 
 At the bottom of each component's notes, list ALL external contributors — not just those with documented features. Any community contributor with **one or more merged PRs** in the milestone should get a mention exactly once in the **Community contributors** section, even if none of their work was promoted into a feature writeup. Use the `community-contribution` label as a strong signal, but do not rely on it exclusively if the merged PR history shows a clear external contribution.
 
-**Vet the list** — the `community-contribution` label is sometimes wrong. Exclude usernames containing `-msft`, `-microsoft`, or other Microsoft suffixes. When in doubt about whether someone is a Microsoft employee, leave them out of the community list.
+**Vet the list** — the `community-contribution` label is sometimes wrong. Exclude usernames containing `-msft`, `-microsoft`, or other Microsoft suffixes. Also exclude bot/automation accounts such as `Copilot`, `dependabot`, `github-actions`, and any account whose name ends in `[bot]` — these aren't community contributors and their profile URLs often don't resolve (e.g. `https://github.com/Copilot` returns 404). When in doubt about whether someone is a Microsoft employee, leave them out of the community list.
 
 **Scope `dotnet/aspnetcore` links to the milestone.** That repo tags every PR with a release milestone (e.g. `11.0-preview4`), so the contributor link should append `+milestone%3A<slug>` to limit it to this milestone's contributions. Look up the exact slug with `gh pr view <pr> --repo dotnet/aspnetcore --json milestone`. Most other source repos don't apply milestones consistently — for those, omit the filter and link to the author's merged PRs without scope.
 

.github/workflows/markdown-link-check.yml

@@ -23,4 +23,4 @@ jobs:
         use-verbose-mode: 'yes'
         check-modified-files-only: 'yes'
         config-file: '.github/workflows/markdown-link-check-config.json'
-        base-branch: 'main'
+        base-branch: ${{ github.base_ref || 'main' }}

.github/workflows/super-linter.yml

@@ -45,5 +45,5 @@ jobs:
           # yamllint disable rule:line-length
           FILTER_REGEX_EXCLUDE: (.github/skills/.*|.github/workflows/copilot-setup-steps\.yml|.github/workflows/.*\.lock\.yml)
           # yamllint enable rule:line-length
-          DEFAULT_BRANCH: main
+          DEFAULT_BRANCH: ${{ github.base_ref || 'main' }}
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

release-notes/11.0/preview/preview5/README.md

@@ -0,0 +1,57 @@
+# .NET 11 Preview 5 - Release Notes
+
+These notes cover the highest-value changes that shipped in .NET 11 Preview 5:
+
+- [Libraries](./libraries.md)
+- [Runtime](./runtime.md)
+- [SDK](./sdk.md)
+- [Containers](./containers.md)
+
+## Languages
+
+- [C#](./csharp.md)
+- [F#](./fsharp.md)
+
+## Web and data
+
+- [.NET MAUI](./dotnetmaui.md)
+- [ASP.NET Core](./aspnetcore.md)
+- [EF Core](./efcore.md)
+
+## Tooling
+
+- [MSBuild](./msbuild.md)
+- [NuGet](./nuget.md)
+- [Windows Forms](./winforms.md)
+- [WPF](./wpf.md)
+
+## Release information
+
+| | Version |
+| --- | --- |
+| Runtime | 11.0.0-preview.5.26276.113 |
+| SDK | 11.0.100-preview.5.26276.113 |
+
+### VMR refs
+
+These release notes were generated from the [dotnet/dotnet](https://github.com/dotnet/dotnet) VMR:
+
+- **Base**: [`v11.0.0-preview.4.26230.115`](https://github.com/dotnet/dotnet/tree/v11.0.0-preview.4.26230.115)
+- **Head**: [`release/11.0.1xx-preview5`](https://github.com/dotnet/dotnet/tree/release/11.0.1xx-preview5)
+
+## Get Started
+
+Instructions on getting started with .NET 11 can be found in the
+[getting started guide](../../get-started.md). Installers and binaries for
+.NET 11 Preview 5 are available from
+[dotnet.microsoft.com](https://dotnet.microsoft.com/download/dotnet/11.0) and
+[.NET 11 Releases](../../README.md).
+
+## Stay up to date
+
+You can find a broader overview of .NET 11 here:
+
+- [What's new in .NET 11](https://learn.microsoft.com/dotnet/core/whats-new/dotnet-11/overview)
+- [What's new in ASP.NET Core for .NET 11](https://learn.microsoft.com/aspnet/core/release-notes/aspnetcore-11)
+- [What's new in EF Core 11](https://learn.microsoft.com/ef/core/what-is-new/ef-core-11.0/whatsnew)
+- [What's new in .NET MAUI in .NET 11](https://learn.microsoft.com/dotnet/maui/whats-new/)