[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
deepmerge	==2.1.0 → ==4.0.0

---

Release Notes

toumorokoshi/deepmerge (deepmerge)

v4.0.0

Compare Source

What's Changed

• Handle mixed dictionary key types in append_unique by @​vitalivo in #​44
• Handle unhashable tuples in append_unique by @​xingzhao-ji in #​47
• (fix with breaking changes): Deduplicate incoming values in append_unique by @​muneikh in #​46

New Contributors

• @​vitalivo made their first contribution in #​44
• @​xingzhao-ji made their first contribution in #​47
• @​muneikh made their first contribution in #​46

Full Changelog: toumorokoshi/deepmerge@v3.0.1...v4.0.0

v3.0.1

Compare Source

What's Changed

• Fix: explicitly re-export public API via __all__ by @​RafaelWO in #​42

New Contributors

• @​RafaelWO made their first contribution in #​42

Full Changelog: toumorokoshi/deepmerge@v3.0...v3.0.1

v3.0

Compare Source

Breaking Changes

• fix: override_if_not_empty should not skip falsy primitives (0, False, 0.0) by @​gaoflow in #​41 (considered a breaking change due to no longer treating falsy values as empty, and the behavior will change for those who may rely on it).

Full Changelog: toumorokoshi/deepmerge@v2.1.0...v3.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

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

Command failed: pipenv lock
Creating a virtualenv for this project
Pipfile: /tmp/renovate/repos/github/osism/openstack-project-manager/Pipfile
Using /usr/local/bin/python 3.10.22 to create virtualenv...
created virtual environment CPython3.10.22.final.0-64-x86_64 in 979ms
  creator 
CPython3Posix(dest=/runner/cache/others/virtualenvs/openstack-project-manager-rl
sV6fXC, clear=False, no_vcs_ignore=False, venv_redirect=None, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, via=copy, 
app_data_dir=/tmp/containerbase/cache/.cache/virtualenv)
    added seed packages: pip==26.2.2, setuptools==84.2.1
  activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator
,PythonActivator,XonshActivator

Successfully created virtual environment!
Virtualenv location: /runner/cache/others/virtualenvs/openstack-project-manager-rlsV6fXC
Locking  dependencies...
ERROR: No matching distribution found for openstacksdk==4.20.0

The conflict is caused by:
    The user requested openstacksdk==4.20.0