chore: (automate) housekeeping #134
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lvlcn-t
added
housekeeping
dependencies
lvlcn-t
requested review from
y-eight,
niklastreml,
puffitos and
eumel8
as code owners
puffitos
reviewed
May 17, 2024
* chore: rm old nolint comment
4 tasks
puffitos
approved these changes
Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
To automate the chore of bumping the deps every now and then.
Closes #78, I've bumped
viperand added the mentioned feature tag to our goreleaser configs.Changes
I've added a
dependabot.ymlconfig and pre-commit workflow that automatically bumps the pre-commit refs on pull requests. For more information refer to https://pre-commit.ci/lite.htmlAdditionally I've removed/adjusted the deprecated linters and configs of the golangci-lint config.
At last I've bumped the go deps, besides
github.com/getkin/kin-openapi v0.124.0because it contained breaking changes.We should bump and fix the errors in another PR.
For additional information look at the commits.
Tests done
None applicable, besides the succeeding github action.
TODO