Update dependency future to v1

openverse-bot commented 2 weeks ago

This PR contains the following updates:

Package	Type	Update	Change
future (source)	project.dependencies	major	`>=0.18.3, <0.19` -> `>=1, <1.1`

Release Notes

PythonCharmers/python-future (future)

### [`v1.0.0`](https://redirect.github.com/PythonCharmers/python-future/releases/tag/v1.0.0) [Compare Source](https://redirect.github.com/PythonCharmers/python-future/compare/v0.18.3...v1.0.0) The new version number of 1.0.0 indicates that the python-future project, like Python 2, is now done. The most important change in this release is adding support for Python 3.12 ([`ba1cc50`](https://redirect.github.com/PythonCharmers/python-future/commit/ba1cc50) and [`a6222d2`](https://redirect.github.com/PythonCharmers/python-future/commit/a6222d2) and [`bcced95`](https://redirect.github.com/PythonCharmers/python-future/commit/bcced95)). This release also includes these fixes: - Small updates to the docs - Add SECURITY.md describing security policy ([`0598d1b`](https://redirect.github.com/PythonCharmers/python-future/commit/0598d1b)) - Fix pasteurize: NameError: name 'unicode' is not defined ([`de68c10`](https://redirect.github.com/PythonCharmers/python-future/commit/de68c10)) - Move CI to GitHub Actions ([`8cd11e8`](https://redirect.github.com/PythonCharmers/python-future/commit/8cd11e8)) - Add setuptools to requirements for building docs ([`0c347ff`](https://redirect.github.com/PythonCharmers/python-future/commit/0c347ff)) - Fix typos in docs ([`350e87a`](https://redirect.github.com/PythonCharmers/python-future/commit/350e87a)) - Make the fix_unpacking fixer more robust ([`de68c10`](https://redirect.github.com/PythonCharmers/python-future/commit/de68c10)) - Small improvements to shell scripts according to shellcheck ([`6153844`](https://redirect.github.com/PythonCharmers/python-future/commit/6153844))

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (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 Renovate Bot.

openverse-bot commented 2 weeks 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: api/pdm.lock

Command failed: pdm update --no-sync --update-eager future
WARNING: Project requires a python version of ==3.12.*, The virtualenv is being created for you as it cannot be matched to the right version.
INFO: python.use_venv is on, creating a virtualenv for this project...
Virtualenv is created successfully at /tmp/renovate/repos/github/WordPress/openverse/api/.venv
[FileNotFoundError]: [Errno 2] No such file or directory: '/home/ubuntu/.local/state'
WARNING: Add '-v' to see the detailed traceback

openverse-bot commented 2 weeks ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

WordPress / openverse