ci: keep Dependabot off action majors and off the build-only NU1903 - #25
Merged
Conversation
Dependabot's first two PRs after #18 both proposed changes this repository had already decided against. #23 bumps upload-artifact to v7 and download-artifact to v8 — release.yml documents why those majors are declined (v8 stops auto-unzipping, which would break the push step on the publish path). #24 "fixes" the NU1903 warning by adding a direct System.Security.Cryptography.Xml reference to the core package: the vulnerable path is Microsoft.EntityFrameworkCore.Design (PrivateAssets=all), which consumers never receive, and the remedy would ship them a dependency they never had to silence a warning that only ever concerned build machines (Directory.Build.props documents keeping it a warning for exactly that reason). The actions ecosystem now ignores semver-major updates — minors and patches still arrive weekly, a major is a deliberate change with a test behind it. A nuget entry for src/ with open-pull-requests-limit 0 proposes no version updates and exists only so security updates there honour its ignore of System.Security.Cryptography.Xml. Both reasons are in the file. Co-Authored-By: Claude Fable 5 <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.
Dependabot's first two PRs after #18 landed (#23, #24) both propose changes this repository had already decided against; this makes those decisions rules Dependabot follows.
upload-artifact→ v7 anddownload-artifact→ v8.release.ymldocuments why those majors are declined — v8 stops auto-unzipping, which would breakPush to NuGetfindingdist/*.nupkgon the publish path. → the actions ecosystem now ignoresversion-update:semver-major; minors and patches still arrive weekly, grouped. A major is a deliberate change with a test behind it.System.Security.Cryptography.Xmlreference to the core package. The vulnerable path isMicrosoft.EntityFrameworkCore.Design(PrivateAssets=all) — consumers never receive it, andDirectory.Build.propskeeps NU1903 a warning for exactly that reason. The remedy would ship every consumer a dependency they never had, to silence a build-machine warning. → anugetentry forsrc/*withopen-pull-requests-limit: 0(no version updates) whose only purpose is that security updates there honour its ignore of that package.Reasons are in the file and in CLAUDE.md.
dependabot.ymlparses;ClaudeMdConsistencyTestspasses.After merging this: close #23 and #24. Dependabot won't recreate them.
🤖 Generated with Claude Code