chore: protected-file changes for v0.2.2 (split from #134)#187
Merged
Conversation
Protected-only PR ahead of the v0.2.2 release (#134, vNext -> main). Extracts just the files the `Detect .NET Projects` guard blocks so the maintainer can admin-bypass a small, reviewable diff — and #134 then merges through the normal ruleset (status checks + review-thread resolution) without a full-diff bypass. Protected files (vNext's merged versions): - .editorconfig - BannedSymbols.txt - Directory.Build.props (analyzers: Meziantou 3.0.115, VS.Threading 18.7.23, Sonar 10.27, SourceLink 10.0.300; PublicApiAnalyzers; SourceLink/snupkg metadata) - .github/workflows/pr.yaml (ReSharper InspectCode job, coverage-parser fixes) - .github/workflows/codeql.yaml (security-extended, action @v4) - .github/workflows/release.yaml (verify-docs-build, .snupkg) - .github/workflows/stryker.yaml (canonical windows-latest mutation workflow) - .github/workflows/benchmarks.yaml (gh-pages concurrency group) `Detect .NET Projects` will fail here by design -> admin-bypass at merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Summary
Protected-only PR ahead of the v0.2.2 release (#134,
vNext → main). It extracts just the files that theDetect .NET Projectsguard blocks, so you can admin-bypass a small, reviewable diff here — and #134 then merges through the normal ruleset (required status checks + review-thread resolution) without bypassing its full release diff.Protected files (vNext's already-merged versions)
.editorconfigBannedSymbols.txtDirectory.Build.props— analyzers (Meziantou 3.0.115, VS.Threading 18.7.23, Sonar 10.27, SourceLink 10.0.300), PublicApiAnalyzers, SourceLink/snupkg metadata.github/workflows/pr.yaml— ReSharper InspectCode job (ci: add ReSharper InspectCode as a parallel required check in pr.yaml #178), coverage-parser fixes.github/workflows/codeql.yaml—security-extended, action@v4.github/workflows/release.yaml—verify-docs-build,.snupkg.github/workflows/stryker.yaml— canonical windows-latest mutation workflow.github/workflows/benchmarks.yaml—gh-pagesconcurrency groupExpected CI
Detect .NET Projects❌ — by design (that's the whole point); admin-bypass at merge.After this merges
I'll merge
mainback intovNextso #134's protected-file delta vanishes and it goes green without a bypass.Source release PR: #134.