⬆️ Updates env-cmd to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
env-cmd	^10.1.0 → ^11.0.0

---

Release Notes

toddbluhm/env-cmd (env-cmd)

v11.0.0

Compare Source

• BREAKING: Drop support for nodejs v8 to v20.9. The minimum supported nodejs version is now v20.10.
• BREAKING: Must use -- to separate the env-cmd flags from the command to execute (env-cmd -f .env -- node index.js).
• BREAKING: Removed -r flag and use only -f flag.
• BREAKING: Support inline comments in .env files. A # character now signifies the start of an inline comment, unless the value is surrounded by quotation marks (").
• BREAKING: Migrated the repository to ESM modules instead of CommonJS.
• BREAKING: Support variable expansion using curly-brace syntax (${MY_VAR}), when the -x option is enabled.
• Feature: Support loading env variables from .cjs and .mjs files.
• Feature: Support loading env variables from .ts, .cts, and .mts files.
• Feature: When loading an invalid JSON file, show the original parse error.
• Feature: Add a more helpful error message when trying to invoke env-cmd as a standalone command.
• Feature: Added support for nested env variables within env files with the --recursive flag
• Docs: clarify how variable expansion works.
• Internal: Replaced Travis CI with GitHub Actions, run unit tests on windows.
• Internal: Configure automatic releases to npm from GitHub Actions
• Internal: Refactor the loader logic, to make it easier to add other loaders.
• Upgrade: Update all dependencies.
• Upgrade: Upgraded all devDependencies

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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.

[github-actions]

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	conventional-changelog-cli@​2.1.1
	jest@​26.6.3
	husky@​5.2.0
	eslint-plugin-node@​11.1.0
	cz-conventional-changelog@​3.3.0
	@​types/​jest@​26.0.22
	eslint-plugin-spellcheck@​0.0.8
	env-cmd@​11.0.0
	eslint-plugin-github@​4.1.3
	@​semantic-release/​commit-analyzer@​8.0.1
	eslint-import-resolver-typescript@​2.4.0
	eslint-plugin-unicorn@​17.2.0
	@​semantic-release/​changelog@​5.0.1
	@​actions/​core@​1.2.7
	@​semantic-release/​release-notes-generator@​9.0.2
	@​actions/​github@​2.2.0
	@​semantic-release/​npm@​7.1.1
	eslint-plugin-jest@​23.20.0
	eslint-plugin-prettier@​3.3.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code in npm @babel/traverse CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2; >= 8.0.0-alpha.0 < 8.0.0-alpha.4 Patched version: 7.23.2 From: package-lock.json → npm/folio@0.3.18 → npm/jest-circus@26.6.3 → npm/jest@26.6.3 → npm/@babel/traverse@7.13.15 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/traverse@7.13.15. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: npm form-data uses unsafe random function in form-data for choosing boundary CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL) Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4 Patched version: 2.5.4 From: package-lock.json → npm/form-data@2.3.3 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/form-data@2.3.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: Prototype Pollution in npm minimist CVE: GHSA-xvch-5gv4-984h Prototype Pollution in minimist (CRITICAL) Affected versions: >= 1.0.0 < 1.2.6; < 0.2.4 Patched version: 1.2.6 From: package-lock.json → npm/@semantic-release/release-notes-generator@9.0.2 → npm/folio@0.3.18 → npm/cz-conventional-changelog@3.3.0 → npm/conventional-changelog-cli@2.1.1 → npm/license-checker@25.0.1 → npm/@semantic-release/npm@7.1.1 → npm/jest-circus@26.6.3 → npm/coveralls@3.1.0 → npm/jest@26.6.3 → npm/minimist@1.2.5 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/minimist@1.2.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.

[github-actions]

Hello from PR Helper

Is your PR ready for review and processing? Mark the PR ready by including #pr-ready in a comment.

If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold in a comment.

[github-actions]

Scan Summary

Tool	Critical	High	Medium	Low	Status
Security Audit for Infrastructure	0	0	0	3	✅

Recommendation

Looks good ✔️