Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
first of all: thanks for this great tool! (I'm using it as part of https://github.com/renovatebot/renovate.)
I noticed that
mod
does not ignore build constraints when upgrading/downgrading Semantic Import Versioning.This PR will change
mod
, so it will ignore go build constraints and upgrade/downgrade Semantic Import Versioning in all.go
files. The flagbuildflags
has been removed, as it makes no sense anymore.There does not seem to be a way to get the golang.org/x/tools/go/packages to ignore build constraints, so I now only use it to get information about all packages and their
GoFiles
plus theIgnoredFiles
(source files that are not part of the package using the current build configuration but that might be part of the package using other build configurations).These files are then parsed using go/parser. Apart from this, the update logic has not changed.
Cheers
Pascal
PS: I also replaced the deprecated call to
ioutil.WriteFile(…)
withos.WriteFile(…)
.