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
go_modules doesn't do vendoring when using replace directive #3250
Package manager/ecosystem
go_modules Manifest contents prior to update
github.com/buger/jsonparser v1.0.0 Updated dependency
github.com/buger/jsonparser v1.1.1 What you expected to see, versus what you actually saw
Above package is just an example, it happens with any update. We have the following replace line in our go.mod file:
While this replacing is very valid and these packages can both be fetched from Github, Dependabot decides that this go.mod can't be vendored, so in the resulting MR it only updated the go.mod, making the go.sum and vendor folder invalid.
If there's any line that starts with replace it's not going to vendor it?
Images of the diff or a link to the PR, issue or logs
It looks like these are a little related: #1193 #1172
Edit: just tested this in a project without a replace directive, it does edit the go.sum in that case, but it still does not update the vendor folder. Created a separate issue for that: #3380
changed the title [-]go_modules doesn't do vendoring when using replace commands[/-][+]go_modules doesn't do vendoring when using replace directive[/+]on Mar 9, 2021
Activity
[-]go_modules doesn't do vendoring when using replace commands[/-][+]go_modules doesn't do vendoring when using replace directive[/+]Bump npm from 7.10.0 to 7.19.1
jerbob92 commentedon Aug 16, 2021
I think this is fixed already.