Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downgrade Go version requirement to 1.20 #2197

Merged
merged 1 commit into from
Sep 8, 2023

Conversation

jamietanna
Copy link
Contributor

As part of the upgrade to Go 1.21, the Go toolchain now requires the
go directive to match the maximum Go version in use in dependencies.

This leads to any transitive dependency on this library to result in a
requirement of the consuming project moving to Go 1.21.

Although in a lot of cases this may not be as problematic, it forces
consumers to migrate, which we don't need to do in this case.

This also requires we bump jwt and httpexpect dependencies, as they've
downgraded, too.


As discussed in oapi-codegen/oapi-codegen#1221 and related change in gofiber/fiber#2614. See also golang/go#62409

Draft until below are merged:

As part of the upgrade to Go 1.21, the Go toolchain now requires the
`go` directive to match the maximum Go version in use in dependencies.

This leads to any transitive dependency on this library to result in a
requirement of the consuming project moving to Go 1.21.

Although in a lot of cases this may not be as problematic, it forces
consumers to migrate, which we don't need to do in this case.

This also requires we bump jwt and httpexpect dependencies, as they've
downgraded, too.
@CLAassistant
Copy link

CLAassistant commented Sep 4, 2023

CLA assistant check
All committers have signed the CLA.

@kataras kataras marked this pull request as ready for review September 8, 2023 16:08
@kataras kataras self-requested a review as a code owner September 8, 2023 16:08
Copy link
Owner

@kataras kataras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I always prefer to use the latest versions to my projects in order to force our developers to upgrade to the latest Go version if they want to upgrade to the latest Iris version. Every single new Go release comes with new security fixes and that's why I prefer latest updates. However, I see that this decision is kind of problematic for you so I am happy to accept and merge this PR. Thank you @jamietanna

@kataras kataras merged commit cf3808a into kataras:main Sep 8, 2023
@jamietanna
Copy link
Contributor Author

Thanks very much @kataras 💜 This will also need #2203 to go in, as the dependencies needed bumping alongside this 🤞

@jamietanna
Copy link
Contributor Author

Thanks very much @kataras 🙌 Would you be OK to push a release when you get a chance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants