🤖 fix: document vendor stamp-file handling#22
Conversation
|
@codex review Please review this PR. |
|
@codex review Addressed CI feedback and updated the PR. |
|
Codex Review: Didn't find any major issues. Nice work! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
@codex review Updated per reviewer direction:
|
|
Codex Review: Didn't find any major issues. Hooray! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
This PR hardens vendor workflow guidance and removes fragile stamp-file behavior that caused CI drift.
Background
Agent runs were deleting
vendorstamp artifacts unexpectedly. The prior Makefile relied onvendor/.modules.stamp, which is not stable undergo mod vendorand led to verify-vendor check failures.Implementation
Makefileto usevendor/modules.txtas the vendor freshness target marker:VENDOR_STAMP := vendor/modules.txttouch/directory creation for.modules.stamp.modules.stampignore handling from.gitignoreAGENTS.mdguidance to explicitly protectvendor/modules.txtand removed.modules.stampreferencesValidation
make verify-vendormake testmake buildmake lintRisks
Low. This aligns stamping with canonical
go mod vendoroutput and reduces CI/local mismatch risk.Generated with
mux• Model:openai:gpt-5.3-codex• Thinking:xhigh• Cost:$0.23