Skip to content

Update submodule to latest master in microsoft/main#2158

Merged
bot-for-go[bot] merged 4 commits intomicrosoft/mainfrom
dev/auto-sync/microsoft/main
Feb 26, 2026
Merged

Update submodule to latest master in microsoft/main#2158
bot-for-go[bot] merged 4 commits intomicrosoft/mainfrom
dev/auto-sync/microsoft/main

Conversation

@bot-for-go
Copy link
Contributor

@bot-for-go bot-for-go bot commented Feb 25, 2026

Hi! I'm a bot, and this is an automatically generated upstream sync PR. 🔃

After submitting the PR, I will attempt to enable auto-merge in the "merge commit" configuration.

For more information, visit sync documentation in microsoft/go-infra.

Copy link

@review-bot-for-go review-bot-for-go bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Auto-approving.

@bot-for-go bot-for-go bot enabled auto-merge February 25, 2026 16:11
@gdams gdams requested a review from a team as a code owner February 25, 2026 20:04
@github-actions
Copy link

✅ Patch Consistency Review - No Issues Found

This PR contains mechanical updates to patches/0004-Use-crypto-backends.patch to maintain compatibility with upstream Go changes. The review confirms:

Changes Analyzed:

  1. Git blob hash updates: Updated index references to reflect upstream file changes

    • fips140only.go: 1b0a4be6ba5897a8d840b17022cc
    • rand.go: 29648b9f386ed700e736a579859a
    • rand_test.go: 3bb3d5f1acda2513e4a65db28bd2
  2. Line number adjustments: Patch context lines updated to match upstream changes

    • fips140only.go: @@ -20,13 +20,20@@ -18,11 +18,18 (upstream removed blank lines)
    • rand_test.go: @@ -154,13 +155,17@@ -156,13 +157,17 (import changes)
  3. Context line updates: Correctly removed references to deleted upstream code

    • Removed ApprovedRandomReader function context (upstream deleted this function)
    • Added crypto/internal/rand import in context (upstream added this import)

Consistency Assessment:

✅ All changes are mechanical updates maintaining patch applicability
✅ No functional modifications to Microsoft-specific code
✅ Patch content consistency maintained across the codebase
✅ Follows guideline to avoid extraneous blank lines
✅ No cross-patch inconsistencies detected

The PR correctly updates the patch file to track upstream changes without altering the actual Microsoft modifications. This is exactly how patch maintenance should work for upstream sync operations.

AI generated by Patch Consistency Review Agent

@bot-for-go bot-for-go bot merged commit df603c7 into microsoft/main Feb 26, 2026
49 checks passed
@bot-for-go bot-for-go bot deleted the dev/auto-sync/microsoft/main branch February 26, 2026 10:11
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