deps(py): bump python-dotenv from 1.2.1 to 1.2.2#86
Conversation
Bumps [python-dotenv](https://github.com/theskumar/python-dotenv) from 1.2.1 to 1.2.2. - [Release notes](https://github.com/theskumar/python-dotenv/releases) - [Changelog](https://github.com/theskumar/python-dotenv/blob/main/CHANGELOG.md) - [Commits](theskumar/python-dotenv@v1.2.1...v1.2.2) --- updated-dependencies: - dependency-name: python-dotenv dependency-version: 1.2.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
|
PR author is in the excluded authors list. |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes. Give us feedback
There was a problem hiding this comment.
Pull Request Overview
Codacy results indicate the PR is up to standards. However, the python-dotenv 1.2.2 release introduces breaking changes for the set_key and unset_key functions—specifically regarding symlink handling and file permission preservation. These changes should be evaluated against the application's environment management strategy. Additionally, there is contradictory information in the upstream documentation regarding Python 3.9 compatibility that warrants caution if that runtime is in use.
About this PR
- The 1.2.2 release introduces breaking changes for
set_keyandunset_key: they no longer follow symlinks by default and now preserve original file permissions instead of forcing 0o600. Ensure this does not conflict with your deployment or local configuration management. - The upstream release notes are contradictory regarding Python 3.9 support, listing it as both 'Added' and 'Dropped'. If the project targets Python 3.9, verify compatibility before merging.
Test suggestions
- Verify that environment variables are still loaded correctly by the application using the updated library.
- If the application uses set_key or unset_key, verify that the new symlink and file permission behaviors do not cause regressions.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that environment variables are still loaded correctly by the application using the updated library.
2. If the application uses set_key or unset_key, verify that the new symlink and file permission behaviors do not cause regressions.
🗒️ Improve review quality by adding custom instructions
Bumps python-dotenv from 1.2.1 to 1.2.2.
Release notes
Sourced from python-dotenv's releases.
Changelog
Sourced from python-dotenv's changelog.
Commits
36004e0Bump version: 1.2.1 → 1.2.2eb20252docs: update changelog for v1.2.2790c5c0Merge commit from fork43340daRemove the use ofshin tests (#612)09d7ceedocs: clarify override behavior and document FIFO support (#610)c8de288ci: improve workflow efficiency with best practices (#609)7bd9e3dAdd Windows testing to CI (#604)1baaf04Drop Python 3.9 support and update to PyPy 3.11 (#608)4a22cf8ci: enable testing on Python 3.14t (free-threaded) (#588)e2e8e77Fix license specifier (#597)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.