Automate analyzer release doc promotion - #479
Merged
Merged
Conversation
Introduces a GitHub Actions workflow to automatically move new analyzer rule entries from `AnalyzerReleases.Unshipped.md` to `AnalyzerReleases.Shipped.md` when a new version tag is pushed. This streamlines the release process and ensures accurate publication of analyzer release notes.
This was referenced Aug 28, 2026
This was referenced Sep 5, 2026
This was referenced Sep 14, 2026
github-actions Bot
pushed a commit
to BenjaminMichaelis/DotnetTemplates
that referenced
this pull request
Sep 17, 2026
Updated [Moq.AutoMock](https://github.com/moq/Moq.AutoMocker) from 4.0.2 to 4.0.3. <details> <summary>Release notes</summary> _Sourced from [Moq.AutoMock's releases](https://github.com/moq/Moq.AutoMocker/releases)._ ## 4.0.3 ## What's Changed * Upgrade core dependencies and align with Roslyn API changes by @Keboo in moq/Moq.AutoMocker#477 * feat: Add Fake Time Provider extension generator by @Keboo in moq/Moq.AutoMocker#478 * Automate analyzer release doc promotion by @Keboo in moq/Moq.AutoMocker#479 * Correct `AutoMocker.Use` instance check to use reference equality by @Keboo in moq/Moq.AutoMocker#503 **Full Changelog**: moq/Moq.AutoMocker@v4.0.2...v4.0.3 Commits viewable in [compare view](moq/Moq.AutoMocker@v4.0.2...v4.0.3). </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 this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This was referenced Sep 18, 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
1 participant
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.
This automates the analyzer release notes handoff so stable releases do not require a manual edit to move entries from
AnalyzerReleases.Unshipped.mdintoAnalyzerReleases.Shipped.md.The workflow now promotes analyzer release docs only for
v*tag pushes and derives the release version directly from the tag name. A small PowerShell script handles the file update by appending the unshipped entries under the matching## Release <version>heading in the shipped file, clearing the moved rule rows from the unshipped file, and skipping prerelease versions.