You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 32fb4f0
Browse filesBrowse the repository at this point in the historyBrowse files
Two Go build breakages were reported as success.
#343: in a project with a committed vendor/ (go mod vendor), wiring a
socket `replace` (apply, vendor, scan --mode hosted) or removing one
(rollback) leaves vendor/modules.txt out of step with go.mod, so every
default build fails with "inconsistent vendoring".
#618: when a patch bumps or adds a requirement in the patched module's
own go.mod, the consumer's go.mod/go.sum are not updated, so the
default -mod=readonly build fails with "updates to go.mod needed".
In both cases apply exited 0 and apply --check said in sync.
A new vendor::go_consumer_sync::audit compares the replace directives
with vendor/modules.txt (go mod vendor / go work vendor layouts) and
with the patched copies' go.mod requirements. apply, vendor, rollback
and hosted scan now emit go_vendor_modules_txt_out_of_sync /
go_requirements_out_of_sync warnings that name the go command to run.
apply --check and vendor --check report them as drift until it is run.
Fixes#343Fixes#618
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
if vendor::jvm::apply::upstream_unverified(entry){
1272
1293
env.warnings.push(RunWarning{code:"vendor_jvm_upstream_unverified".into(),detail:format!("{key}: upstream metadata was accepted offline; run vendor online to verify registry checksums")});
0 commit comments