New version of dotenv (16.4.5) broke the build

[depfu[bot]]

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
dotenv	^16.0.3	16.4.5

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of dotenv for this test run.

What changed?

✳️ dotenv (^16.0.3 → 16.4.5) · Repo · Changelog

Release Notes

16.4.5 (from changelog)

Changed

• 🐞 fix recent regression when using path option. return to historical behavior: do not attempt to auto find .env if path set. (regression was introduced in 16.4.3) #814

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 6 commits:

• 16.4.5
• Merge pull request #814 from motdotla/dont-check-existance
• changelog 🪵
• adjust logic to support tests
• do not check if exists
• rename .env-multiline to .env.multiline

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
next-wordpress-starter	❌ Failed (Inspect)		Feb 21, 2024 6:56am