8 Commits (82c9789a9a64dc9ca5c726c866b9ab22f543f514)

Author	SHA1	Message	Date
Icarus Wu	b635089c7c	all: remove deprecated protobuf dependencies (#30232) ... The package `github.com/golang/protobuf/proto` is deprecated in favor `google.golang.org/protobuf/proto`. We should update the codes to recommended package. Signed-off-by: Icarus Wu <icaruswu66@qq.com>	3 months ago
jwasinger	41abab9e39	build: add check for stale generated files (#30037) ... Co-authored-by: Felix Lange <fjl@twurst.com>	4 months ago
jwasinger	a4e338f05e	accounts/usbwallet/trezor: upgrade to generate with protoc 27.1 (#30058)	4 months ago
Peter Straus	1a79089193	fix: update outdated link to trezor docs (#28966) ... fix: update link to trezor	9 months ago
Felix Lange	b628d72766	build: upgrade to go 1.19 (#25726) ... This changes the CI / release builds to use the latest Go version. It also upgrades golangci-lint to a newer version compatible with Go 1.19. In Go 1.19, godoc has gained official support for links and lists. The syntax for code blocks in doc comments has changed and now requires a leading tab character. gofmt adapts comments to the new syntax automatically, so there are a lot of comment re-formatting changes in this PR. We need to apply the new format in order to pass the CI lint stage with Go 1.19. With the linter upgrade, I have decided to disable 'gosec' - it produces too many false-positive warnings. The 'deadcode' and 'varcheck' linters have also been removed because golangci-lint warns about them being unmaintained. 'unused' provides similar coverage and we already have it enabled, so we don't lose much with this change.	2 years ago
Péter Szilágyi	1a83114c74	all: update author list and licenses	5 years ago
Péter Szilágyi	b4cc7b660c	accounts/usbwallet: recreate Trezor protocol, support old and new	6 years ago
benma	dddd6ef006	accounts/usbwallet/trezor: expose protobuf package (#17980) ... When some of the same messages are redefined anywhere in a Go project, the protobuf package panics (see https://github.com/golang/protobuf/issues/178). Since this package is internal, there is no way to work around it, as one cannot use it directly, but also cannot define the same messages. There is no downside in making the package accessible.	6 years ago