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
What you expected to see, versus what you actually saw
I expected Dependabot to resolve my dependencies inside a submodule. Instead, it appears to have not initialized the submodule, as when it attempts to find go.mod in the submodule via go mod replace directive, it fails to find it:
updater | ERROR <job_113688959> Error processing github.com/getsentry/sentry-go (Dependabot::DependabotError)
updater | ERROR <job_113688959> go: github.com/OurOrg/[email protected] (replaced by ./some_submodule): reading some_submodule/go.mod: open /some_submodule/go.mod: no such file or directory
To be clear, I am not trying to have Dependabot manage/update the version of the submodule. I just want Dependabot to manage the dependencies in the root go.mod file, but it is failing to resolve due to errors like the one shown above.
The text was updated successfully, but these errors were encountered:
Coming back to this, it seems dependabot does resolve submodules properly now, however I was still seeing 404s trying to access the submodule when I viewed the dependabot logs
Package ecosystem
gomod
Manifest location and content prior to update
/go.mod
/some_submodule/go.mod
dependabot.yml content
What you expected to see, versus what you actually saw
I expected Dependabot to resolve my dependencies inside a submodule. Instead, it appears to have not initialized the submodule, as when it attempts to find go.mod in the submodule via go mod replace directive, it fails to find it:
To be clear, I am not trying to have Dependabot manage/update the version of the submodule. I just want Dependabot to manage the dependencies in the root go.mod file, but it is failing to resolve due to errors like the one shown above.
The text was updated successfully, but these errors were encountered: