Update django-health-check digest to 00eaa7e

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
django-health-check	tool.uv.sources	digest	53f9bdc → 00eaa7e

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[github-actions]

OpenAPI Changes

Show/hide ## Changes for v0.yaml:

## Changes for v0.yaml:


## Changes for v1.yaml:


## Changes for v2.yaml:

Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).

[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: uv.lock

Command failed: uv lock --upgrade-package django-health-check
Using CPython 3.11.15 interpreter at: /opt/containerbase/tools/python/3.11.15/bin/python3
   Updating https://github.com/revsys/django-health-check (00eaa7e154ee307d58e7346a631e91f19894c62a)
    Updated https://github.com/revsys/django-health-check (00eaa7e154ee307d58e7346a631e91f19894c62a)
  × No solution found when resolving dependencies:
  ╰─▶ Because only django-health-check==4.1.3.dev1+g00eaa7e15 is available
      and django-health-check==4.1.3.dev1+g00eaa7e15 depends on django>=5.2,
      we can conclude that all versions of django-health-check depend on
      django>=5.2.
      And because your project depends on django==5.1.15 and
      django-health-check, we can conclude that your project's requirements
      are unsatisfiable.