Update dependency dynaconf to v3.3.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
dynaconf	==3.3.2 → ==3.3.4

---

Release Notes

dynaconf/dynaconf (dynaconf)

v3.3.4

Compare Source

Bug Fixes

• Fixed error when passing a list values for env on dynaconf init (#​1278) (#​1421). By @​apoorvdarshan.

• Clean up nested dynaconf_merge tokens when parent key is new (#​1435). By @​Sanjays2402.

• Keep sibling keys that share a dotted path leaf name (#​1434). By @​Sanjays2402.

• Convert container subclasses (#​1436). By @​deepakganesh78.

• Django early validation integration code bug (#​1432). By @​pedro-psb.

Chore

v3.3.3

Compare Source

Bug Fixes

• Fixed regression on lazy evaluation when using dynaboxify=False (#​1429). By @​pedro-psb.

Docs

• Clarify the values of True, False and None for must_exist check (#​1416). By @​pedro-psb.

Chore

• Fix netlify deploy command on publish workflow (#​1420). By @​pedro-psb.

• Consolidate docs-publishing workflow for rolling-release (#​1417). By @​pedro-psb.

• Simplify docs-only skip and include backport branches on main CI (#​1415). By @​pedro-psb.

---

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/python3 3.10.20 to create virtualenv...
created virtual environment CPython3.10.20.final.0-64-x86_64 in 1940ms
  creator 
CPython3Posix(dest=/runner/cache/others/virtualenvs/openstack-project-manager-rl
sV6fXC, clear=False, no_vcs_ignore=False, 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, setuptools==83.0.0
  activators 
BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator
,PythonActivator,XonshActivator

✔ Successfully created virtual environment!
Virtualenv location: /runner/cache/others/virtualenvs/openstack-project-manager-rlsV6fXC
Locking  dependencies...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Ignored the 
following versions that require a different python version: 4.14.0 
Requires-Python >=3.11; 4.15.0 Requires-Python >=3.11; 4.16.0 Requires-Python 
>=3.11; 4.17.0 Requires-Python >=3.11
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Could not 
find a version that satisfies the requirement openstacksdk==4.17.0 (from 
versions: 0.6.0, 0.6.1, 0.6.2, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.8.0, 0.8.1, 
0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.6, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 
0.9.6, 0.9.7, 0.9.8, 0.9.9, 0.9.10, 0.9.11, 0.9.12, 0.9.13, 0.9.14, 0.9.15, 
0.9.16, 0.9.17, 0.9.18, 0.9.19, 0.10.0, 0.11.0, 0.11.1, 0.11.2, 0.11.3, 0.11.4, 
0.12.0, 0.13.0, 0.14.0, 0.15.0, 0.16.0, 0.17.0, 0.17.1, 0.17.2, 0.17.3, 0.18.0, 
0.18.1, 0.19.0, 0.20.0, 0.21.0, 0.22.0, 0.23.0, 0.24.0, 0.25.0, 0.26.0, 0.27.0, 
0.27.1, 0.28.0, 0.29.0, 0.30.0, 0.31.0, 0.31.1, 0.31.2, 0.32.0, 0.33.0, 0.34.0, 
0.35.0, 0.36.0, 0.36.1, 0.36.2, 0.36.3, 0.36.4, 0.36.5, 0.37.0, 0.38.0, 0.39.0, 
0.40.0, 0.41.0, 0.42.0, 0.43.0, 0.44.0, 0.45.0, 0.46.0, 0.46.1, 0.47.0, 0.48.0, 
0.49.0, 0.50.0, 0.51.0, 0.52.0, 0.53.0, 0.54.0, 0.55.0, 0.55.1, 0.56.0, 0.57.0, 
0.58.0, 0.59.0, 0.60.0, 0.61.0, 0.62.0, 0.99.0, 0.100.0, 0.101.0, 0.102.0, 
0.103.0, 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.5.0, 1.5.1, 
2.0.0, 2.1.0, 3.0.0, 3.1.0, 3.2.0, 3.3.0, 4.0.0, 4.0.1, 4.1.0, 4.2.0, 4.3.0, 
4.4.0, 4.5.0, 4.6.0, 4.7.0, 4.7.1, 4.7.2, 4.8.0, 4.9.0, 4.10.0, 4.11.0, 4.12.0, 
4.13.0)
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
Hint: try $ pipenv lock --verbose to see the full dependency resolution output.
ERROR: No matching distribution found for openstacksdk==4.17.0
The conflict is caused by:
    The user requested openstacksdk==4.17.0

Traceback (most recent call last):
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.10.20/lib/python3.10/site-packages/p
ipenv/routines/lock.py", line 94, in do_lock
    venv_resolve_deps(
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.10.20/lib/python3.10/site-packages/p
ipenv/utils/resolver.py", line 1467, in venv_resolve_deps
    c = resolve(cmd, st, project=project)
  File 
"/opt/containerbase/tools/pipenv/2026.6.2/3.10.20/lib/python3.10/site-packages/p
ipenv/utils/resolver.py", line 1240, in resolve
    raise ResolutionFailure("Failed to lock Pipfile.lock!")
pipenv.exceptions.ResolutionFailure: ERROR: Failed to lock Pipfile.lock!