To give users more flexibility - someone using our API but still stuck on 1.21 can still use it. If we enforce 1.22 they can not. Someone using 1.22 can use 1.21 without issues.
Usually we want to target the previous release of go for the most flexibility for users of our code, older versions (1.20 and prior) aren't supported by the go maintainers anymore so we shouldn't target them.
We have been using the newest release of go for the last 2 or 3 versions for go-spacemesh because it had improvements that we always benefitted from immediately - maybe reconsider this for when 1.23 comes out and then stick with 1.22 until we have to upgrade.
To give users more flexibility - someone using our API but still stuck on 1.21 can still use it. If we enforce 1.22 they can not. Someone using 1.22 can use 1.21 without issues.
Usually we want to target the previous release of go for the most flexibility for users of our code, older versions (1.20 and prior) aren't supported by the go maintainers anymore so we shouldn't target them.
We have been using the newest release of go for the last 2 or 3 versions for
go-spacemeshbecause it had improvements that we always benefitted from immediately - maybe reconsider this for when 1.23 comes out and then stick with 1.22 until we have to upgrade.