- Notifications
You must be signed in to change notification settings - Fork868
rfcs: Supported Go versions policy#1769
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
Signed-off-by: Paulo Gomes <pjbgf@linux.com>
| Current state (`.github/workflows/test.yml`): | ||
| ```yaml | ||
| matrix: | ||
| go-version: [1.24.x, 1.25.x] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This can be even simpler:
| go-version:[1.24.x, 1.25.x] | |
| go-version:[oldstable, stable] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
TIL, nice recommendation@alexandear. 🙇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Likewise, this is so much better 👍🏻
| ### Go Directive Policy | ||
| The `go.mod` file's `go` directive will always be set to `N-1`, where `N` is the latest stable Go version. This means: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
When exactly does the bump happen after a Go release? Day one? After a month for ecosystem stabilization?
This RFC opens up the discussion around the support Go versions policy, proposing to officially support only the last 2 stable Go release lines, reducing from the current policy of supporting the last 3 stable release lines.