Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Dependency Dashboard

Open
#239 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
django, docker-compose, elasticsearch, github-actions, python
Domain
ci-cd, devops, tooling

Research direction

Start with the Dependency Dashboard documentation, then inspect the pending entries in pyproject.toml, .pre-commit-config.yaml, docker-compose.yml, .github/workflows/, and renovate.json5. Because this issue does not select one update, define a specific dependency scope first; done would mean the selected update is applied and the relevant checks pass.

Written by the indexing model from the issue text.

Description

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
View this repository on the Mend.io Web Portal.

Abandoned Dependencies

The following dependencies have not received updates for an extended period and may be unmaintained.

[!NOTE]
Packages are marked as abandoned when they exceed the abandonmentThreshold since their last release. Unlike deprecated packages with official notices, abandonment is detected by release inactivity.

View abandoned dependencies (1)
Datasource Package Last Updated
pre-commit pre-commit/pre-commit-hooks 2025-08-09

Awaiting Schedule

The following updates are awaiting their schedule. To get an update now, click on a checkbox below.

  • Update j178/prek-action action to v3.1.0
  • Update pre-commit Dependencies (adamchainz/django-upgrade, zizmorcore/zizmor-pre-commit)
  • Update Python Packages (coverage, prek, pytz)
  • Update Python Tools (astral-sh/ruff-pre-commit, astral-sh/setup-uv, ruff, tox-dev/pyproject-fmt, uv)
  • Lock file maintenance
  • 🔐 Create all awaiting schedule PRs at once 🔐

Detected Dependencies

docker-compose (1)
docker-compose.yml
github-actions (3)
.github/workflows/git-hooks.yml (3)
  • actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1
  • j178/prek-action v3.0.0@4e14d07f9231acabce116ccfca13b13dd9755ece → [Updates: v3.1.0]
  • ubuntu 26.04
.github/workflows/release.yml (4)
  • actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1
  • astral-sh/setup-uv v10.1.0@bec219d24cd3e171d82865faccec33120bb574f4 → [Updates: v10.3.2]
  • actions/attest v4.2.2@1e69f48acb82d1966a394da916b4c1698aa569d6
  • ubuntu 26.04
.github/workflows/tests.yml (3)
  • actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1
  • astral-sh/setup-uv v10.1.0@bec219d24cd3e171d82865faccec33120bb574f4 → [Updates: v10.3.2]
  • ubuntu 26.04
poetry (1)
pyproject.toml (11)
  • django >=5.2,<6.2
  • django-haystack >=3.3.0,<4
  • djangorestframework >=3.16
  • prek ==0.5.4 → [Updates: ==0.5.7]
  • ruff ==0.16.8 → [Updates: ==0.17.2]
  • coverage ==7.16.2 → [Updates: ==7.17.0]
  • elasticsearch ==7.17.13
  • geopy ==2.5.0
  • pytz ==2026.4 → [Updates: ==2026.5]
  • sphinx ==9.0.4
  • sphinx-rtd-theme ==3.1.0
pre-commit (1)
.pre-commit-config.yaml (8)
  • pre-commit/pre-commit-hooks v6.0.0
  • tox-dev/pyproject-fmt v2.29.4 → [Updates: v2.30.3]
  • adamchainz/django-upgrade 1.32.0 → [Updates: 1.33.0]
  • astral-sh/ruff-pre-commit v0.16.8 → [Updates: v0.17.2]
  • zizmorcore/zizmor-pre-commit v1.30.1 → [Updates: v1.31.1]
  • google/yamlfmt v0.21.0
  • pyjson5 ==2.0.1
  • python-jsonschema/check-jsonschema 0.38.2 → [Updates: 0.39.0]
regex (2)
.github/workflows/release.yml (2)
  • python 3.14
  • uv 0.12.17 → [Updates: 0.13.5]
.github/workflows/tests.yml (1)
  • uv 0.12.17 → [Updates: 0.13.5]
renovate-config (1)
renovate.json5 (1)
  • ulgens/renovate-presets v0.0.11

  • Check this box to trigger a request for Renovate to run again on this repository
Dominant language
Python
Stars
264
Forks
81
Avg merge
23h 27m
Merged PRs (30d)
3

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from django-commons/drf-haystack

All issues in django-commons/drf-haystack

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.