Tags: edgarulg/kleat
Tags
chore(deps): Upgrade golangci-lint (spinnaker#141) * chore(deps): Upgrade golangci-lint Also, the documentation recommends running it separately from other jobs so that they run in parallel. The main reason I'm doing that here is because there are a lot of warnings in the logs that I think are because it is expecting to start with a clean working environment, which is not the case when it runs after our other checks. * chore(dependencies): Use v2 of the golanglint-ci action * chore(deps): Upgrade setup-go
chore(deps): bump github.com/google/go-cmp from 0.5.1 to 0.5.2 (spinn… …aker#134) Bumps [github.com/google/go-cmp](https://github.com/google/go-cmp) from 0.5.1 to 0.5.2. - [Release notes](https://github.com/google/go-cmp/releases) - [Commits](google/go-cmp@v0.5.1...v0.5.2) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
fix(release): Fix changelog generation (spinnaker#105) Every kleat release was generating a full changelog of all commits ever made rather than only those since the last release. The reason for this is that we were not fetching tags when cloning the repository, so when go-releaser used 'git describe' to find the last tag, it was not finding one and thus generating a changelog of all commits ever made. This could be fixed by adding a --tags to the unshallow command, but it looks like the github action will fetch tags if you pass depth=0 to it (which means fetch all commits) so let's do that instead. It looks like in the two weeks since we added this config, go-releaser has updated their docs to now suggest adding depth=0 to the checkout command (whereas they previously had the unshallow command that was broken).
fix(core): Address ignored fields from test halconfig (spinnaker#102) * fix(test): Remove unused fields from test halconfig This commit removes fields that are not used by kleat from the test halconfig. * feat(proto): Add some missing protos These are fields that Halyard defaults but doesn not expose commands for editing (though users can still manuall set them). In order to preserve backwards-compatibility for users migrating from Halyard we should still support reading them. Ideally the fields should be defaulted to something sensible in the service, but this will not affect migrating users who already have them specified. * fix(proto): Fix mis-spelled requiredGroupMembership This was incorrectly included as requiredGroupMemberships in a number of protos. * feat(proto): Remove experimental flag As we're not using optional protos, remove the experimental flag as we don't need it anymore. * chore(core): Bump deps and run go mod tidy