Bump python-dotenv from 1.2.1 to 1.2.2 in /examples/snowflake_cortex/dagster_snowflake

[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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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.

Greptile Summary

This PR bumps python-dotenv from 1.2.1 to 1.2.2 and tightens the lower bound in pyproject.toml to >=1.2.2. The uv.lock update is mostly expected, but it also contains an unrelated change: the dagster dependency specifier shifts from ==1.12.10 to >=1.9.0, which does not match any change in pyproject.toml and suggests the lock file was regenerated with a different constraint set.

• The dagster specifier in uv.lock (>=1.9.0) diverges from pyproject.toml's apparent pin (==1.12.10), which could cause users who run uv sync to resolve a different (potentially newer or older) dagster version than intended.

Confidence Score: 4/5

Safe to merge after verifying the dagster specifier change in uv.lock is intentional or correcting the mismatch.

The python-dotenv bump itself is straightforward, but the lock file contains an unrelated dagster constraint loosening (==1.12.10 → >=1.9.0) that does not correspond to any pyproject.toml change, which is a P1 concern worth addressing before merge.

examples/snowflake_cortex/dagster_snowflake/uv.lock — the dagster specifier divergence needs clarification.

Important Files Changed

Filename	Overview
examples/snowflake_cortex/dagster_snowflake/pyproject.toml	Bumps python-dotenv lower bound from >=1.0.0 to >=1.2.2 to match the new locked version
examples/snowflake_cortex/dagster_snowflake/uv.lock	Updates python-dotenv to 1.2.2, but also unexpectedly loosens the dagster pin from ==1.12.10 to >=1.9.0 and removes several s390x greenlet wheel entries

Prompt To Fix All With AI

This is a comment left during a code review.
Path: examples/snowflake_cortex/dagster_snowflake/uv.lock
Line: 789-790

Comment:
**Unexpected dagster specifier change**

The lock file reflects a change from a pinned `dagster==1.12.10` to `dagster>=1.9.0`, but this is not present in `pyproject.toml` and is unrelated to the python-dotenv bump. This means the lock file may have been regenerated with a different resolution state than `pyproject.toml` actually declares. If `pyproject.toml` still pins `dagster==1.12.10`, this divergence could cause unexpected behavior when users run `uv sync` and get a different dagster version than intended.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "Bump python-dotenv in /examples/snowflak..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Unexpected dagster specifier change

The lock file reflects a change from a pinned dagster==1.12.10 to dagster>=1.9.0, but this is not present in pyproject.toml and is unrelated to the python-dotenv bump. This means the lock file may have been regenerated with a different resolution state than pyproject.toml actually declares. If pyproject.toml still pins dagster==1.12.10, this divergence could cause unexpected behavior when users run uv sync and get a different dagster version than intended.

Prompt To Fix With AI

This is a comment left during a code review.
Path: examples/snowflake_cortex/dagster_snowflake/uv.lock
Line: 789-790

Comment:
**Unexpected dagster specifier change**

The lock file reflects a change from a pinned `dagster==1.12.10` to `dagster>=1.9.0`, but this is not present in `pyproject.toml` and is unrelated to the python-dotenv bump. This means the lock file may have been regenerated with a different resolution state than `pyproject.toml` actually declares. If `pyproject.toml` still pins `dagster==1.12.10`, this divergence could cause unexpected behavior when users run `uv sync` and get a different dagster version than intended.

How can I resolve this? If you propose a fix, please make it concise.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pypi/​python-dotenv@​1.2.2

View full report