Skip to content

Protected config for v0.13.1 release: protected-only PR ahead of #192#231

Merged
Chris-Wolfgang merged 1 commit into
mainfrom
protected/d8-release-v0.13.1-config
Jun 19, 2026
Merged

Protected config for v0.13.1 release: protected-only PR ahead of #192#231
Chris-Wolfgang merged 1 commit into
mainfrom
protected/d8-release-v0.13.1-config

Conversation

@Chris-Wolfgang

Copy link
Copy Markdown
Owner

Protected-only PR extracted from the v0.13.1 release branch (vNext, #192) so the larger release diff can merge through full ruleset enforcement instead of an all-or-nothing admin bypass.

Why this PR exists

The Detect .NET Projects guard fails any PR touching protected config files, requiring an admin bypass — but a bypass waives all ruleset rules at once (including required review-thread resolution). Splitting the protected files into this minimal PR lets them get a focused manual review + bypass here, while #192 merges normally with every rule enforced.

Protected files included

  • .editorconfig
  • .github/workflows/codeql.yaml
  • .github/workflows/pr.yaml
  • .github/workflows/release.yaml
  • .github/workflows/stryker.yaml
  • BannedSymbols.txt
  • Directory.Build.props

Expected CI

  • Detect .NET Projects ❌ — expected; this is the guard the split exists to satisfy. Admin-bypass merge after reviewing the diff.
  • Stage 1/2/3 SKIPPED (depend on the guard output).
  • Other security scans ✅.

After merge

Merge main back into vNext so #192's protected-file delta vanishes and it becomes mergeable without bypass.

Follows: #192

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant