* Lint fixes
* Use latest go version for go-check
Fixes nil pointer issue in staticcheck
* Add test_analysis helper script
* Use custom go-test-template
* Add some tests to the test_analysis script
* Always upload test_results db
* Attempt to fix test on windows
* Better if statement
* Try to fix flaky test
* Disable caching setup-go on Windows
* Better if statement
* Tweak
* Always upload summary and artifact
* Close db
* No extra newline
* Add failing proto test
* Add a new proto compilation script
A proto file's *import path* is relative to one of the `--proto-path`s.
Previously, the proto files were compiled separately. Some invocations
used different values for the `--proto_path`, which led to inconsistent
import paths in proto file descriptors.
Typically, this wouldn't be a problem. However, if a downstream project
uses `protoregistry.GlobalFiles` to inspect proto dependencies, it will fail
to find a dependency's file descriptor when the dependency was compiled
with a different `--proto_path`.
By using a single script to generate all protobuf files, we can ensure
the `--proto_path` is always set to the same sane value (the root of the
project, as suggested in the [official documentation]).
[official documentation]: https://protobuf.dev/programming-guides/proto2/#importing
* Add go_package options so scripts/gen-proto.sh succeeds
* Remove undesirable `go:generate protoc` directives
* Run `go generate ./...`
* Script uses arrays, I think we need bash
---------
Co-authored-by: Marco Munizaga <git@marcopolo.io>
1. A simple checklist.
2. A script to generate release notes.
I'm explicitly ignoring anything like a branching model for the moment.
We don't have a long RC process so that shouldn't be required (yet).
