chore(deps): update dependency @dotenvx/dotenvx to v1.34.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@dotenvx/dotenvx	1.29.0 -> 1.34.0

---

Release Notes

dotenvx/dotenvx (@​dotenvx/dotenvx)

v1.34.0

Compare Source

Added

• main.set method now writes to files (#​517)

v1.33.0

Compare Source

Added

• support ESM import convenience import '@​dotenvx/dotenvx/config' (#​508)

v1.32.1

Compare Source

Changed

• remove duplicated help messages (#​504)

v1.32.0

Compare Source

Added

• add encrypted check support for ext prebuild (#​501)

Changed

• modify ext precommit to check git modified state as well as git staged state - useful for using dotenvx ext precommit without the --install flag in automated scripts and ci. (#​499)

Removed

• remove internal logger methods errorvp, errorvpb, warnv, warnvp, warnvpb, successvp, successvpb, help2 (#​501)

v1.31.3

Compare Source

Changed

• adjust wingetcreate to use powershell when parsing version

v1.31.2

Compare Source

Changed

• use wingetcreate for releasing to WinGet (#​498)

v1.31.1

Compare Source

Changed

• 🐞 fix encryption of values containing explicit \n newlines (#​495)

v1.31.0

Compare Source

Added

• expose main.set function (#​492)
• add missing types for main.config (#​491)

v1.30.1

Compare Source

Added

• support complex command substitution combining variable expansion (#​490)

v1.30.0

Compare Source

Added

• add -fk (--env-keys-file) flag to customize the path to your .env.keys file with run, get, set, encrypt, decrypt, and keypair 🎉 (#​486)

This is great for monorepos. Maintain one .env.keys file across all your apps.

$ dotenvx encrypt -fk .env.keys -f apps/backend/.env
$ dotenvx encrypt -fk .env.keys -f apps/frontend/.env

$ tree -a .
├── .env.keys
└── apps
    ├── backend
    │   └── .env
    └── frontend
        └── .env

$ dotenvx get -fk .env.keys -f apps/backend/.env

---

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 was generated by Mend Renovate. View the repository job log.

[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: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"^9.16.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"8.18.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         @typescript-eslint/eslint-plugin@"^5.4.2 || ^6.0.0 || ^7.0.0 || ^8.0.0" from [email protected]
npm error         node_modules/eslint-config-next
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   8 more (@typescript-eslint/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.23.0 || ^8.0.0" from [email protected]
npm error node_modules/eslint-config-next
npm error   dev eslint-config-next@"14.2.20" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.23.0 || ^8.0.0" from [email protected]
npm error   node_modules/eslint-config-next
npm error     dev eslint-config-next@"14.2.20" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-28T22_31_09_165Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-28T22_31_09_165Z-debug-0.log

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
pangea-ai-chat	⬜️ Ignored (Inspect)	Visit Preview		Jan 28, 2025 10:31pm