Update dependency dotenv-expand to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
dotenv-expand	10.0.0 -> 11.0.6

---

Release Notes

motdotla/dotenv-expand (dotenv-expand)

v11.0.6

Compare Source

Changed

• Fix .nyc_output in .npmignore

v11.0.5

Compare Source

Changed

• 🐞 fix recursive expansion when expansion key is sourced from process.env (#​121)

v11.0.4

Compare Source

Changed

• 🐞 fix recursive expansion when expansion keys in reverse order (#​118)

v11.0.3

Compare Source

Changed

• 🐞 bug fix when processEnv set to process.env rather than empty object (also test fixes which hid the bug) (#​113)

v11.0.2

Compare Source

Changed

• Changed funding link in package.json to dotenvx.com

v11.0.1

Compare Source

Added

• Added funding link in package.json

v11.0.0

Compare Source

Added

• Add typings for import dotenv-expand/config (#​99)
• Support expansion of dot in env variable names like POSTGRESQL.BASE.USER (#​93)
• Add processEnv option (#​105)
• Add support for default format of ${VAR-default} (#​109)

Changed

• Do not expand prior process.env environment variables. NOTE: make sure to see updated README regarding dotenv.config({ processEnv: {} }) (#​104)
• 🐞 handle $var1$var2 (#​103, #​104)
• 🐞 fix fatal recursive error when variable defines value with same variable VAR=$VAR #​98

Removed

• Remove ignoreProcessEnv option (use processEnv option going forward)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 21 workspace projects
Progress: resolved 0, reused 1, downloaded 0, added 0
.                                        |  WARN  deprecated @babel/[email protected]
Progress: resolved 78, reused 65, downloaded 0, added 0
Progress: resolved 138, reused 124, downloaded 0, added 0
packages/next                            |  WARN  deprecated @babel/[email protected]
packages/next                            |  WARN  deprecated @babel/[email protected]
packages/next                            |  WARN  deprecated @babel/[email protected]
packages/next                            |  WARN  deprecated @types/[email protected]
/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/third-parties:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/next/-/next-13.5.0.tgz: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/third-parties

No authorization header was set for the request.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 887a0b3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR