we need this linter to actually tell us where problems occur

.github/workflows/golangci-lint.yml

@@ -18,7 +18,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v2
         with:
-          go-version: ^1.18
+          go-version: ^1.20
       - name: Run golangci-lint
         uses: golangci/golangci-lint-action@v3
         with:

.golangci.yaml

@@ -12,6 +12,7 @@ linters:
     - interfacer
     - nosnakecase
     - tparallel
+    - nonamedreturns
     - exhaustruct
     - stylecheck
     - gosec
@@ -54,6 +55,32 @@ linters:
     - tagliatelle
     - nilnil
 
+# output configuration options
+output:
+  # Format: colored-line-number|line-number|json|tab|checkstyle|code-climate|junit-xml|github-actions|teamcity
+  #
+  # Multiple can be specified by separating them by comma, output can be provided
+  # for each of them by separating format name and path by colon symbol.
+  # Output path can be either `stdout`, `stderr` or path to the file to write to.
+  # Example: "checkstyle:report.xml,json:stdout,colored-line-number"
+  #
+  # Default: colored-line-number
+  format: json
+  # Print lines of code with issue.
+  # Default: true
+  print-issued-lines: true
+  # Print linter name in the end of issue text.
+  # Default: true
+  print-linter-name: true
+  # Make issues output unique by line.
+  # Default: true
+  uniq-by-line: true
+  # Add a prefix to the output file references.
+  # Default is no prefix.
+  path-prefix: ""
+  # Sort results by: filepath, line and column.
+  sort-results: false
+
 issues:
   exclude-rules:
     # The existing ETSI lints have some gnarly logic that needs