build(deps): bump github.com/GaijinEntertainment/go-exhaustruct from v3.3.1 to 4.0.0

[xobotyi]

• analyzer package is now distributed via vanity import as dev.gaijin.team/go/exhaustruct/v4.
• version introduced new features which, in turn, required usage of structure as configuration causing major version bump.
• updated documentation on config fields to be more obvious.

GaijinEntertainment/go-exhaustruct@v3.3.1...v4.0.0

For golangci-lint users nothing changes, except 4 new fields added, so no deprecations or migration on the users side is required.
Major bump of exhaustruct caused mostly because of package rename and the way config being passed to the linter.

note: go mod tidy touched more packages than i've expected

[CLAassistant]

All committers have signed the CLA.

[ldez]

This PR is based on golangci-lint v1 (the branch master).

The PR must target the branch main (golangci-lint v2).

The way to manage major (breaking) versions of linters has changed:

• dev: handle linter major versions #5848
• build(deps): bump github.com/bombsimon/wsl/v5 from 4.7.0 to 5.0.0 #5900
• dev: add suggested migration for linter configuration #5902

[xobotyi]

For golangci-lint users configuration itself still the same, just extra fields added and functionally without enabling new fields linter still acts the same.

Updated description regarding that.

[ldez]

ok, if there are no breaking changes, you don't need to use the new approach.

[xobotyi]

dang it! i see the issue now, the branch is wrong..

[xobotyi]

ready for review
note that this pr requires bumping go.mod go version to 1.24

[ldez]

You must downgrade your min go version inside your linter.

[xobotyi]

Welp, it is transitory.
Package we use is 1.24, and therefore linter is also.
IIRC golangci-lint targets oldstable, so it can be safely transitioned whenever 1.25 version support lands.

[ldez]

Your linter doesn't need go1.24: the module dev.gaijin.team/go/golib must downgrade the min Go version.

[ldez]

The min Go version is about the language (the syntax), a library should not enforce the latest stable version of Go unless it uses language-specific syntax related to this version.

In all cases, a library should not do that.

GaijinEntertainment/golib#1

[xobotyi]

Linter itself will become dependant on 1.24 next minor release, because of usage of iterators on go types.

golib will also receive direct dependencies to features added in 1.24
there are features requiring these versions, just changes itself are not landed yet..

[ldez]

OK so I will not do more review or merge your PR until go1.25

[xobotyi]

No problems, I've expected that =)

[ldez]

LGTM

[xobotyi]

Unexpectedly soon🤭
I thought of like.. At least 3 weeks of waiting (at the moment of creation)

[ldez]

The official summer release of Go is always around the 15th

https://go.dev/wiki/Go-Release-Cycle

[xobotyi]

1.11 was in September, but.. Whatever)
It's here.

[ldez]

Go 1.11 was released in August (2018-08-24)

Version	Release Date
Go 1.24	2025-02-11 (February)
Go 1.23	2024-08-13 (August)
Go 1.22	2024-02-06 (February)
Go 1.21	2023-08-08 (August)
Go 1.20	2023-02-01 (February)
Go 1.19	2022-08-02 (August)
Go 1.18	2022-03-15 (March)
Go 1.17	2021-08-16 (August)
Go 1.16	2021-02-16 (February)
Go 1.15	2020-08-11 (August)
Go 1.14	2020-02-25 (February)
Go 1.13	2019-09-03 (September)
Go 1.12	2019-02-25 (February)
Go 1.11	2018-08-24 (August)
Go 1.10	2018-02-16 (February)
Go 1.9	2017-08-24 (August)
Go 1.8	2017-02-16 (February)
Go 1.7	2016-08-15 (August)
Go 1.6	2016-02-17 (February)
Go 1.5	2015-08-19 (August)
Go 1.4	2014-12-10 (December)
Go 1.3	2014-06-18 (June)
Go 1.2	2013-12-01 (December)
Go 1.1	2013-05-13 (May)
Go 1	2012-03-28 (March)

https://go.dev/doc/devel/release