chore: update agents.md - #7229
Merged
Merged
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
PR Reviewer Guide 🔍
|
Contributor
|
PeterSchafer
enabled auto-merge
September 5, 2026 13:18
octavian-snyk
approved these changes
Sep 7, 2026
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
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.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Clarify dependency update in agents.md
Where should the reviewer start?
How should this be manually tested?
What's the product update that needs to be communicated to CLI users?
Note
Low Risk
Documentation-only change to agent instructions; no runtime, build, or dependency behavior changes.
Overview
Adds a Handling
go.sumand private modules subsection under Updating Go Dependencies inAGENTS.md.The new text tells agents and contributors to refresh
go.mod/go.sumonly viago get,go mod tidy, ormake tidy, and not to hand-editgo.sumbecause entries must stay lexicographically sorted. It documents usinggo mod tidy -ewhen private modules (e.g.ambient-canary) prevent a normal tidy, and gives a last-resort workflow for manualgo.sumedits (insert in sorted order, then runsort -c go.sum).Reviewed by Cursor Bugbot for commit 5a47a57. Bugbot is set up for automated code reviews on this repo. Configure here.