mirror of
https://github.com/renovatebot/renovate.git
synced 2025-01-15 09:06:25 +00:00
a340830ee6
Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: Michael Kriese <michael.kriese@visualon.de> |
||
---|---|---|
.. | ||
__fixtures__ | ||
__snapshots__ | ||
artifacts.spec.ts | ||
artifacts.ts | ||
extract.spec.ts | ||
extract.ts | ||
index.ts | ||
readme.md | ||
types.ts | ||
update.spec.ts | ||
update.ts |
You might be interested in the following postUpdateOptions
:
gomodTidy
- if you'd like Renovate to rungo mod tidy
after every update before raising the PR- This is implicitly enabled for major updates if the user has enabled the option
gomodUpdateImportPaths
- This is implicitly enabled for major updates if the user has enabled the option
gomodTidy1.17
- if you'd like Renovate to rungo mod tidy -compat=1.17
after every update before raising the PRgomodTidyE
- if you'd like Renovate to rungo mod tidy -e
after every update before raising the PRgomodUpdateImportPaths
- if you'd like Renovate to update your source import paths on major updates before raising the PRgomodMassage
- to enable massaging of allreplace
statements prior to runninggo
so that they will be ignored
When Renovate is running using binarySource=docker
(such as in the hosted Mend Renovate app) then it will pick the latest compatible version of Go to run, i.e. the latest 1.x
release.
Even if the go.mod
has a version like go 1.14
, Renovate will treat it as a ^1.14
constraint and not =1.14
.
Indirect updates are disabled by default. To enable them, add a package rule such as:
{
"packageRules": [
{
"matchManagers": ["gomod"],
"matchDepTypes": ["indirect"],
"enabled": true
}
]
}