Skip to content

Maintenance: nuget-locks - #91

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
connie/maintenance/nuget-locks-4462f50f23fb-32b898692fc0
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
connie/maintenance/nuget-locks-4462f50f23fb-32b898692fc0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Applies the bounded nuget-locks recipe to main at 4462f50.

CI must validate this exact head, including Windows UI and installer checks. Automatic merging also requires enforced, strict branch protection. Release version changes require human review.

Supersedes #80: the same package versions, with the lock files of every project that references the updated ones restored. Dependabot closes #80 once this merges.

SumaFile-Maintenance: nuget-locks
SumaFile-Source: 4462f50
SumaFile-Dependabot: 80@2da6df4b5202715f2c6bbb78e1953bc3e2bf60a5
conniecombs pushed a commit that referenced this pull request Nov 18, 2026
A proposal is a single commit on the main it was computed from, and the gate
insists on current main, so one that main has moved past can never merge; a
lock-file repair is pointless once the Dependabot pull request it took its
versions from is closed or has moved (#91 sat open and conflicting after #81
merged the same versions first). On every run the gate now closes such
proposals with a note saying why. A failure in the sweep is logged and does
not hold up the merge the gate was dispatched for.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LHHmiakAiWjSbfi56QXNjd
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