[deps]: Update python-dotenv to v1

renovate[bot] commented 4 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
python-dotenv	`0.21.1` -> `1.0.1`

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

theskumar/python-dotenv (python-dotenv)

### [`v1.0.1`](https://togithub.com/theskumar/python-dotenv/blob/HEAD/CHANGELOG.md#101---2024-01-23) [Compare Source](https://togithub.com/theskumar/python-dotenv/compare/v1.0.0...v1.0.1) **Fixed** - Gracefully handle code which has been imported from a zipfile (\[[#456](https://togithub.com/theskumar/python-dotenv/issues/456)] by \[[@samwyma](https://togithub.com/samwyma)]) - Allow modules using load_dotenv to be reloaded when launched in a separate thread (\[[#497](https://togithub.com/theskumar/python-dotenv/issues/497)] by \[[@freddyaboulton](https://togithub.com/freddyaboulton)]) - Fix file not closed after deletion, handle error in the rewrite function (\[[#469](https://togithub.com/theskumar/python-dotenv/issues/469)] by \[[@Qwerty-133](https://togithub.com/Qwerty-133)]) **Misc** - Use pathlib.Path in tests (\[[#466](https://togithub.com/theskumar/python-dotenv/issues/466)] by \[[@eumiro](https://togithub.com/eumiro)]) - Fix year in release date in changelog.md (\[[#454](https://togithub.com/theskumar/python-dotenv/issues/454)] by \[[@jankislinger](https://togithub.com/jankislinger)]) - Use https in README links (\[[#474](https://togithub.com/theskumar/python-dotenv/issues/474)] by \[[@Nicals](https://togithub.com/Nicals)]) ### [`v1.0.0`](https://togithub.com/theskumar/python-dotenv/blob/HEAD/CHANGELOG.md#100) [Compare Source](https://togithub.com/theskumar/python-dotenv/compare/v0.21.1...v1.0.0) **Fixed** - Drop support for python 3.7, add python 3.12-dev ([#449](https://togithub.com/theskumar/python-dotenv/issues/449) by \[[@theskumar](https://togithub.com/theskumar)]) - Handle situations where the cwd does not exist. ([#446](https://togithub.com/theskumar/python-dotenv/issues/446) by \[[@jctanner](https://togithub.com/jctanner)])

Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), 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 has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 4 months ago

⚠️ 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: poetry.lock

Updating dependencies
Resolving dependencies...

The current project's supported Python range (>=3.7.17) is not compatible with some of the required packages Python requirement:
  - python-dotenv requires Python >=3.8, so it will not be satisfied for Python >=3.7.17,<3.8

Because bitwarden-event-logs depends on python-dotenv (1.0.1) which requires Python >=3.8, version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties

    For python-dotenv, a possible solution would be to set the `python` property to ">=3.8"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

eliykat commented 3 months ago

@mzieniukbw I see that v1 drops support for Python 3.7, am I right in thinking we can't upgrade this until Splunk support > 3.7?

EDIT: can you please link me to any info about Splunk's Python versioning support?

mzieniukbw commented 3 months ago

@eliykat it's actually hard to find in their documentation https://docs.splunk.com/Documentation/Splunk/9.2.2/Python3Migration/PythonCompatibility To revise apps for compatibility with Splunk Enterprise version 8.x and higher, Python code should generally be made compatible with Python 3.7 or higher. also https://docs.splunk.com/Documentation/Splunk/9.2.2/Python3Migration/AboutMigration says: In future releases, Splunk will support Python version 3.9 and higher. Splunk also plans to deprecate support for Python 3.7.

renovate[bot] commented 3 months ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

bitwarden / splunk