renovate/lib/manager/gomod
2021-12-04 07:12:27 +01:00
..
__fixtures__ feat(gomod): dynamic version detection (#6419) 2020-06-03 10:39:29 +02:00
__snapshots__ fix(gomod): Do not tidy go.mod on major update without gomodUpdateImportPaths (#11976) 2021-10-20 11:28:09 +00:00
artifacts.spec.ts refactor(git): Extract types to separate file (#12855) 2021-11-26 20:36:17 +00:00
artifacts.ts refactor: exec types (#12942) 2021-12-04 07:12:27 +01:00
extract.spec.ts test: fix lint (#12551) 2021-11-08 13:16:58 +01:00
extract.ts fix: refactor regex to use re2 (#12216) 2021-10-20 04:38:49 +00:00
index.ts refactor: introduce enum programming-language (#12052) 2021-10-13 10:54:40 +00:00
readme.md fix(gomod): Do not tidy go.mod on major update without gomodUpdateImportPaths (#11976) 2021-10-20 11:28:09 +00:00
update.spec.ts fix: replace numbered capture group replaces with named capture groups (#12315) 2021-10-25 20:21:21 +02:00
update.ts fix: replace numbered capture group replaces with named capture groups (#12315) 2021-10-25 20:21:21 +02:00

You might be interested in the following postUpdateOptions:

  1. gomodTidy - if you'd like Renovate to run go mod tidy after every update before raising the PR.
    1. This is implicitly enabled for major updates if the user has enabled the option gomodUpdateImportPaths
  2. gomodUpdateImportPaths - if you'd like Renovate to update your source import paths on major updates before raising the PR.

When Renovate is running using binarySource=docker (such as in the hosted WhiteSource Renovate app) then it will pick the latest compatible version of Go to run, i.e. the latest 1.x release. Therefore even if the go.mod contains a version like go 1.14, you will see Renovate treating that as a ^1.14 constraint and not =1.14.