Bump python-dotenv from 1.2.1 to 1.2.2

[dependabot]

Bumps python-dotenv from 1.2.1 to 1.2.2.

Release notes

Sourced from python-dotenv's releases.

v1.2.2

Added

• Support for Python 3.14, including the free-threaded (3.14t) build. (#)

Changed

• The dotenv run command now forwards flags directly to the specified command by @​bbc2 in theskumar/python-dotenv#607
• Improved documentation clarity regarding override behavior and the reference page.
• Updated PyPy support to version 3.11.
• Documentation for FIFO file support.
• Support for Python 3.9.

Fixed

• Improved set_key and unset_key behavior when interacting with symlinks by @​bbc2 in #790c5
• Corrected the license specifier and added missing Python 3.14 classifiers in package metadata by @​JYOuyang in theskumar/python-dotenv#590

Breaking Changes

• dotenv.set_key and dotenv.unset_key used to follow symlinks in some situations. This is no longer the case. For that behavior to be restored in all cases, follow_symlinks=True should be used.

• In the CLI, set and unset used to follow symlinks in some situations. This is no longer the case.

• dotenv.set_key, dotenv.unset_key and the CLI commands set and unset used to reset the file mode of the modified .env file to 0o600 in some situations. This is no longer the case: The original mode of the file is now preserved. Is the file needed to be created or wasn't a regular file, mode 0o600 is used.

Misc

• skip 000 permission tests for root user by @​burnout-projects in theskumar/python-dotenv#561
• Bump actions/checkout from 5 to 6 in the github-actions group by @​dependabot[bot] in theskumar/python-dotenv#593
• Add Windows testing to CI by @​bbc2 in theskumar/python-dotenv#604
• Improve workflow efficiency with best practices by @​theskumar in theskumar/python-dotenv#609
• Remove the use of sh in tests by @​bbc2 in theskumar/python-dotenv#612

New Contributors

• @​JYOuyang made their first contribution in theskumar/python-dotenv#590
• @​burnout-projects made their first contribution in theskumar/python-dotenv#561
• @​cpackham-atlnz made their first contribution in theskumar/python-dotenv#597

Full Changelog: theskumar/python-dotenv@v1.2.1...v1.2.2

Changelog

Sourced from python-dotenv's changelog.

[1.2.2] - 2026-03-01

Added

• Support for Python 3.14, including the free-threaded (3.14t) build. (#588)

Changed

• The dotenv run command now forwards flags directly to the specified command by [@​bbc2] in #607
• Improved documentation clarity regarding override behavior and the reference page.
• Updated PyPy support to version 3.11.
• Documentation for FIFO file support.
• Dropped Support for Python 3.9.

Fixed

• Improved set_key and unset_key behavior when interacting with symlinks by [@​bbc2] in [790c5c0]
• Corrected the license specifier and added missing Python 3.14 classifiers in package metadata by [@​JYOuyang] in #590

Breaking Changes

• dotenv.set_key and dotenv.unset_key used to follow symlinks in some situations. This is no longer the case. For that behavior to be restored in all cases, follow_symlinks=True should be used.

• In the CLI, set and unset used to follow symlinks in some situations. This is no longer the case.

• dotenv.set_key, dotenv.unset_key and the CLI commands set and unset used to reset the file mode of the modified .env file to 0o600 in some situations. This is no longer the case: The original mode of the file is now preserved. Is the file needed to be created or wasn't a regular file, mode 0o600 is used.

Commits

• 36004e0 Bump version: 1.2.1 → 1.2.2
• eb20252 docs: update changelog for v1.2.2
• 790c5c0 Merge commit from fork
• 43340da Remove the use of sh in tests (#612)
• 09d7cee docs: clarify override behavior and document FIFO support (#610)
• c8de288 ci: improve workflow efficiency with best practices (#609)
• 7bd9e3d Add Windows testing to CI (#604)
• 1baaf04 Drop Python 3.9 support and update to PyPy 3.11 (#608)
• 4a22cf8 ci: enable testing on Python 3.14t (free-threaded) (#588)
• e2e8e77 Fix license specifier (#597)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[amrit110]

Security Vulnerabilities — Partial Fix Applied, Some Unfixable

aieng-bot has applied all available security fixes to this PR. The following packages have been upgraded to address pip-audit findings:

✅ Fixed

Package	Old Version	New Version	CVEs Fixed
pillow	12.1.1	≥12.2.0	CVE-2026-42310
pymdown-extensions	10.18	≥10.21.3	CVE-2026-46338
idna	3.11	≥3.15	CVE-2026-45409
pip	26.0.1	≥26.1	CVE-2026-3219, CVE-2026-6357
pytest	9.0.2	≥9.0.3	CVE-2025-71176
urllib3	2.6.3	≥2.7.0	PYSEC-2026-142, PYSEC-2026-141

❌ No Patch Available Yet

The following vulnerabilities cannot be auto-fixed because no fully-patched version has been released to PyPI:

Package	Version	Vulnerability	Status
torch	2.9.1	PYSEC-2026-139	No fix available on PyPI
torch	2.9.1	CVE-2025-3000	No fix available on PyPI
torch	2.9.1	CVE-2025-3001	Fix: 2.10.0 (but still has 2 unfixable CVEs; risky major upgrade)
transformers	4.57.3	PYSEC-2025-217	No fix available on PyPI
transformers	4.57.3	CVE-2026-1839	Fix: 5.0.0rc3 (RC only; but still has 1 unfixable CVE)

Why this cannot be fully auto-merged

The vulnerabilities in torch (PYSEC-2026-139, CVE-2025-3000) and transformers (PYSEC-2025-217) have no fix version released to PyPI yet. Even bumping to the partially-fixed versions (torch 2.10.0, transformers 5.0.0rc3) would leave unfixable CVEs active and risks breaking compatibility (numpy<2.0.0 constraint, RC stability).

Recommended next steps

1. Monitor the torch and transformers vulnerability advisories for complete patch releases
2. Evaluate whether torch>=2.10.0 and transformers>=5.0.0rc3 can be safely adopted (human review required)
3. Consider temporarily adding PYSEC-2026-139, CVE-2025-3000, PYSEC-2025-217 to the ignore-vulns list with a justification comment if these are deemed acceptable risks

This PR cannot be auto-merged until the remaining vulnerabilities are resolved.

Partial fixes applied by aieng-bot

[amrit110]

Automated fix applied and PR merged

The agentic fix loop successfully fixed this PR and merged it.

✓ Successfully fixed merge_conflict failures - Modified 1 files - Executed 171 agent actions - (73 info, 45 tool_call, 9 error, 31 tool_result, 13 reasoning)

View detailed trace on dashboard | Raw trace

AI Engineering Maintenance Bot