Builds Fail with 1.5.0 of subosito/gotenv

[arhea]

Preflight Checklist

• I have searched the issue tracker for an issue that matches the one I want to file, without success.
• I am not looking for support or already pursued the available support channels without success.
• I have checked the troubleshooting guide for my problem, without success.

Viper Version

1.16.0

Go Version

1.20

Config Source

Environment variables

Format

Dotenv

Repl.it link

No response

Code reproducing the issue

No response

Expected Behavior

Package to build.

Actual Behavior

/go/pkg/mod/github.com/spf13/viper@v1.16.0/internal/encoding/dotenv/codec.go:51:33: cannot use &buf (value of type *bytes.Buffer) as gotenv.Reader value in argument to gotenv.StrictParse: *bytes.Buffer does not implement gotenv.Reader (missing method ReadAt)
failed to build, error: exit status 1

Steps To Reproduce

1. Upgrade dependencies of project resulting in subosito/gotenv v1.5.0
2. Error message listed above.
3. Adding replace github.com/subosito/gotenv => github.com/subosito/gotenv v1.4.2 to go.mod, builds succeed.

Additional Information

subosito/gotenv#27

[github-actions]

👋 Thanks for reporting!

A maintainer will take a look at your issue shortly. 👀

In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.

⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9

📣 If you've already given us your feedback, you can still help by spreading the news,
either by sharing the above link or telling people about this on Twitter:

https://twitter.com/sagikazarmark/status/1306904078967074816

Thank you! ❤️

[guybarnhartmagen]

this is a duplicate of #1601

[andig]

That is actually closed. Is it possible that this is a consequence of not requiring a Go version that has bytes.Buffer implement ReadAt?

[arhea]

It looks like the issue I opened on subosito/gotenv#27 has been resolved, thank you @subosito! As for #1601 it looks like that was created shortly after this issue (#1600), apologies for the duplicates.

I have confirmed with 1.6.0 that is working again.

I think it is safe to close this issue.