unexpected upgradable dependencies at first level

[gen2thomas]

This behavior seems to be caused by some of the modules which are required with "// indirect" in go.mod.

Such pending upgrades can not be resolved automatically (e.g. by "go get -u ./..." ).

It looks like such dependencies will be included to go.mod (causing first level) but comes normally from a deeper level, so most likely such deptree items should be filtered, possibly by a further switch (CLI parameter).