Skip to content

Conversation

@selfhoster1312
Copy link

I noticed CI was failing on #20 but i could not reproduce because the version of golangci-lint is so old… so i updated to latest github actions release, and tested with the latest golangci-lint release.

I had to remove some linters i have no idea what they do but they don't exist anymore. Some migration stuff was documented here but not everything because we were so old (our config wasn't even versioned so the migrate subcommand failed to validate).

Anyway i'm not sure it'll pass yet so let's pray to the CI gods :)

@selfhoster1312 selfhoster1312 force-pushed the update-ci branch 6 times, most recently from 8c7f7f4 to 8986a5c Compare September 6, 2025 08:24
@selfhoster1312 selfhoster1312 force-pushed the update-ci branch 2 times, most recently from 6b8fdbb to f1bb981 Compare September 6, 2025 08:47
@selfhoster1312
Copy link
Author

Sooooo i spent a few hours playing robot with my keyboard and monkeytyping stuff to get the CI working. I'm disabled a few imho useless lints, and there's just 2 left that don't pass and i think are important and require some level of review:

  • musttag
  • gosec

Otherwise on this branch golangci-lint should run without simply comparing errors with the previous commit which is a terrible way to accumulate tech debt and let it fall on the first person submitting a PR.

Feel free to review. In particular, this commit deserves special attention: d47a7dc

Because i have no idea what i'm doing in there i'm merely working around the linter errors and i don't know what's the idiomatic way to handle defer/goroutine errors in golang.

@selfhoster1312 selfhoster1312 changed the title DRAFT: meta: Update golangci-lint to v2.X meta: Update CI and follow linter suggestions Sep 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant