Update unparam

[FGasper]

Dependabot seems to have missed this one, which was fixed weeks ago.

[ldez]

The branch master is related to v1 but the v1 is now locked: #5300 (comment)

[FGasper]

@ldez Are you saying this crash can’t be fixed except in v2?

[ldez]

Your question feels a bit aggressive.

Do you read the related issue?

[FGasper]

@ldez I didn’t mean to be aggressive and am sorry to have come across that way.

I’m just wondering how this issue can be fixed. main doesn’t work for us because it currently rejects our v1 config files. The contributor docs still say to open PRs against master.

[ldez]

@FGasper I think you can understand that I will not create a bug fix for v1 unless special circumstances because the maintenance of the v1 should stop at some point, even if there are bugs.

If I begin to accept v1 modifications, the maintenance will never stop.

So I need to define a "rule", and this "rule" will be valid only before the v2 release: I invite your company (MongoDB Inc.) to sponsor the project.

• https://donate.golangci.org/
• https://donate.ldez.dev/

Like that, maintenance is constrained through time and money, I think it's fair.

The v2 release should happen very soon.

My initial plan was to create a v2 release 3 days ago, but I spent those days diagnosing a complex bug and doing v2 preparation and checks.