Alert RelEng when a new go.mod lands on main - #11871
Draft
stpierre wants to merge 1 commit into
Draft
Conversation
A new Go module can be added anywhere in the tree without Release Engineering hearing about it, and RelEng owns tooling that has to know about every module. Nothing announces one today: tests/mixedbrain/go.mod landed in temporalio#10413 with no signal. Add a push-to-main workflow that diffs the push range for added go.mod files and posts them to Slack. Notify-only, never blocking: adding a module is legitimate, it just needs RelEng follow-up. `testdata/` and `vendor/` are excluded. Fixes RE-587 Co-Authored-By: Claude Opus 5 (1M context) <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.
What changed?
Add a push-to-main workflow that diffs the push range for added go.mod files and posts them to #alerts-release-engineering. Notify-only, never blocking: adding a module is legitimate, it just needs RelEng follow-up. testdata/ and vendor/ are excluded.
Why?
Release tooling assumed a single root
go.modand needs adjustments when a new one is added, which has caused issues in two recent cloud releases.How did you test it?