Bump go-build-tools to v0.1.0

[bogdandrutu]

Signed-off-by: Bogdan Drutu bogdandrutu@gmail.com

[codecov]

Codecov Report

Merging #2839 (a3c8e83) into main (f86225b) will increase coverage by 0.0%.
The diff coverage is n/a.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #2839   +/-   ##
=====================================
  Coverage   69.3%   69.3%           
=====================================
  Files        145     145           
  Lines       6729    6729           
=====================================
+ Hits        4664    4667    +3     
+ Misses      1950    1948    -2     
+ Partials     115     114    -1     

Impacted Files	Coverage Δ
samplers/jaegerremote/sampler_remote.go	87.4% <0.0%> (+1.9%)	⬆️

[MadVikingGod]

Looks like this is the culprit. We can add a replace back to v1.12.0 until golangci-lint fixes this behavior.

[MadVikingGod]

A summary for anyone interested.

• Viper v1.13.0 changed so that all keys of nested maps will be transformed to lowercase. This was the intended behavior; they consider this a bug fix and won't change the behavior.
• golangci-lint and multimod use viper; if either is upgraded to v1.13.0 they will break our current config.
• golangci-lint marshals the yaml in .golangci.yaml to generate the config passed to linters. Specifically, revive.
• revive doesn't use viper and looks for the specific argument string.
• So the net effect is what was a golangci config for two particular linters in revive used a map[] for their arguments and are now seeing these panics with golangci-lint v1.15.0 because of the viper change. We use one of them.

I think our options are:

1. Use a replace for viper v1.12.0 until this is ironed out upstream
2. Disable the context-as-argument linter until this is sorted upstream.

[bogdandrutu]

@MadVikingGod do you want me to add the replace?

[MrAlias]

Looks like viper does not have a plan to fix the issue: spf13/viper#1431

[MadVikingGod]

The community agreed that disabling the linter, for the time being, is the better option. #2878 is the fix specifically for that. This can merge after.

[pellared]

This PR is outdated.