12 Commits

Author	SHA1	Message	Date
leo	fc53e2a66a	ci: bump golangci-lint to v1.50.1	2023-01-13 22:18:17 +01:00
leo	3f77c573a6	chore: 2023	2023-01-12 23:35:51 +01:00
leo	68b14f9960	chore: add all updates, sort out later	2022-12-24 11:30:22 +01:00
surtur	3acc856046	golangci: use version cmd instead of '--version'	2022-09-01 21:52:29 +02:00
surtur	0f6b4b95c6	golangci: bump to 1.49.0	2022-09-01 21:10:10 +02:00
surtur	14281e8dd1	golangci-lint: bump to 1.48.0 ... ifshort linter has been deprecated in the meanwhile so comment it out.	2022-09-01 20:38:08 +02:00
surtur	c79de3ad38	ci: bump golangci-lint to v1.47.3	2022-08-03 17:49:20 +02:00
surtur	034f485539	ci: install golangci-lint from source ... using pre-built binaries absolutely *can* bite, e.g. in case of env/compile-time Go version mismatch (think golangci-lint built with go1.18 vs ran with go1.19 that is present in the env), which is why from now on it is going to be built right in the environment where it's going to be used with whatever version of Go is present there, that *will* guarantee it's able to run there. why the golangci-lint project (used to) discourage installation from sources (or using `go install`) is still beyond me (yeah, Reasons). refs: https://github.com/golangci/golangci-lint-action/issues/442#issuecomment-1203786890 https://github.com/golangci/golangci-lint-action/issues/530 https://github.com/golangci/golangci-lint-action/issues/540 # similar issue (the exact same, really) exhibited way earlier than go1.19... https://github.com/golangci/golangci-lint/issues/2673	2022-08-03 17:45:20 +02:00
surtur	496ddc191a	ci: refresh in parallel	2022-07-16 22:09:08 +02:00
surtur	cb5d8b8931	ci: ping godocs.io to re-fetch sources	2022-07-08 22:36:55 +02:00
surtur	b1278f431b	ci: '`' -> '"'	2022-06-17 02:15:35 +02:00
surtur	0f8f3bbef3	ci: add .drone.star + badges	2022-06-14 17:31:59 +02:00