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

Update go.mod to reflect that afero requires go >= 1.15.10 #346

Merged
merged 1 commit into from Apr 1, 2022
Merged

Update go.mod to reflect that afero requires go >= 1.15.10 #346

merged 1 commit into from Apr 1, 2022

Conversation

jeffwidman
Copy link
Contributor

@jeffwidman jeffwidman commented Mar 16, 2022

As explained in #291 (comment), now that
afero supports io/fs.FS, it requires go >= 1.15.10.

Rather than pinning to 1.15 and occasionally confusing users who are
on < 1.15.10, I thought simplest to jump straight to 1.16.

Especially given 1.18 was just released, the upstream go team no
longer even supports 1.15.

The change to go.sum was the result of running go mod tidy.

As explained in
#291 (comment), now that
`afero` supports `io/fs.FS`, it requires `go` >= `1.15.10`.

Rather than pinning to `1.15` and occasionally confusing users who are
on < `1.15.10`, I thought simplest to jump straight to `1.16`.

Especially given `1.18` was just released, the upstream `go` team no
longer even supports `1.16`.

The change to `go.sum` was the result of running `go mod tidy`.
@jeffwidman jeffwidman changed the title Bump minimum go version to 1.16 Update go.mod to reflect that afero requires go >= 1.15.10 Mar 16, 2022
@0xmichalis 0xmichalis merged commit 100c9a6 into spf13:master Apr 1, 2022
1 check passed
@jeffwidman jeffwidman deleted the bump-minimum-go-version branch April 1, 2022 22:20
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.

None yet

2 participants