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 }}
This repository was archived by the owner on Sep 9, 2020. It is now read-only.
The automated vendor verification introduced in #1912 is lovely, but it's definitely going to cause problems for some people. We need to add another field to Gopkg.toml that allows the user to designate projects (not packages, whole projects) for which verification should be skipped.
Skipping verification means that:
dep ensure will have to unconditionally write out such projects, in much the same way that it used to unconditionally write out all projects to vendor
dep check (per dep: Introduce dep check subcommand #1932) may or may not still print notices for non-verified projects when they come back from vendor verification as changed, but even if it does, it won't error if there's a hash mismatch.
The text was updated successfully, but these errors were encountered:
The automated vendor verification introduced in #1912 is lovely, but it's definitely going to cause problems for some people. We need to add another field to
Gopkg.toml
that allows the user to designate projects (not packages, whole projects) for which verification should be skipped.Skipping verification means that:
dep ensure
will have to unconditionally write out such projects, in much the same way that it used to unconditionally write out all projects tovendor
dep check
(per dep: Introduce dep check subcommand #1932) may or may not still print notices for non-verified projects when they come back from vendor verification as changed, but even if it does, it won't error if there's a hash mismatch.The text was updated successfully, but these errors were encountered: