go-utils
go-utils copied to clipboard
solo-io
golang utilities
Bumps [github.com/gogo/protobuf](https://github.com/gogo/protobuf) from 1.3.1 to 1.3.2. Release notes Sourced from github.com/gogo/protobuf's releases. Release v.1.3.2 Tested versions: go 1.15.6 protoc 3.14.0 Bug fixes: skippy peanut butter Commits b03c65e skippy peanut butter...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
When listing the dependency bumps in our changelogs, we should sanitize them to only output the latest semver bump for a specific repo/dependency. For example, in Gloo OSS release [v1.15.0-beta5](https://github.com/solo-io/gloo/releases/tag/v1.15.0-beta5)...
# Changes Added code to only generate the latest dependency bumps on release. When following semantic versioning `v[MAJOR][.MINOR][.PATCH]`, we only get the latest bump in the list of dependency bumps....
Part of: https://github.com/solo-io/gloo-mesh-enterprise/issues/1127
Per [discussion doc](https://docs.google.com/document/d/1WSIydrjed6N6FHpxYfOJAER7PrQs1ckgy5XazwsTYpQ/edit), changelog bot should support _nested_ versions. This looks like: ``` v1.9 v1.9.0 v1.9.1 v1.9.2 v1.10 v1.10.1 v1.10.2 v1.10.3 ... ``` Notably, this looks like almost the _exact...
Today it compares all releases. We should either use a predicate or a reasonable max release set up for it.
This can cause the changelog-bot to fail to find a valid changelog if there are >300 modifications that are alphanumerically prior to the location of the changelog file. This is...
When we output the security scan docs gen file, the order of the images scanned within a particular version is non-deterministic. Every time we re-run it it changes. This wasn't...
We have an existing security scanning utility (https://github.com/solo-io/go-utils/tree/master/securityscanutils) which is used by various teams to run Trivy scans against release images on a consistent basis. For example, in Gloo Edge,...
Currently gogoutils are located in gloo, but they should be located in go-utils
