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

Dependency Dashboard

Open
#2 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
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, docker-compose, github-actions, postgres, python

Research direction

Start with the linked Renovate Dependency Dashboard documentation, then inspect pyproject.toml, compose.yml, docker/postgres/Dockerfile, docker/python/Dockerfile, and .github/workflows/python.yml. The issue is an automated collection of dependency and image updates with several linked pull requests, so it has no single newcomer-sized completion criterion.

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.

Config Migration Needed

  • Select this checkbox to let Renovate create an automated Config Migration PR.

Rate-Limited

The following updates are currently rate-limited. To force their creation now, click on a checkbox below.

  • chore(deps): update dependency pytest-asyncio to ^0.26.0
  • chore(deps): update dependency python-dateutil to v2.9.0
  • fix(deps): update dependency aiosqlite to ^0.22.0
  • fix(deps): update dependency asyncpg to ^0.32.0
  • fix(deps): update dependency injector to ^0.24.0
  • chore(deps): update actions/checkout action to v7
  • chore(deps): update codecov/codecov-action action to v7
  • chore(deps): update dependency flake8 to v7
  • chore(deps): update dependency mypy to v2
  • chore(deps): update dependency pip-licenses to v5
  • chore(deps): update dependency pyproject-flake8 to v7
  • chore(deps): update dependency pytest-asyncio to v1
  • chore(deps): update dependency pytest-cov to v7
  • chore(deps): update postgres docker tag to v17
  • 🔐 Create all rate-limited PRs at once 🔐

Open

The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.

Detected Dependencies

docker-compose (1)
compose.yml
dockerfile (2)
docker/postgres/Dockerfile (1)
  • postgres 14.5-bullseye → [Updates: 14.18-bullseye, 17.5-bullseye]
docker/python/Dockerfile (1)
  • python 3.11-slim → [Updates: 3.14-slim]
github-actions (1)
.github/workflows/python.yml (11)
  • actions/checkout v2 → [Updates: v7]
  • satackey/action-docker-layer-caching v0.0.11
  • actions/checkout v2 → [Updates: v7]
  • satackey/action-docker-layer-caching v0.0.11
  • actions/checkout v2 → [Updates: v7]
  • satackey/action-docker-layer-caching v0.0.11
  • actions/checkout v2 → [Updates: v7]
  • satackey/action-docker-layer-caching v0.0.11
  • actions/checkout v2 → [Updates: v7]
  • satackey/action-docker-layer-caching v0.0.11
  • codecov/codecov-action v3 → [Updates: v7]
poetry (1)
pyproject.toml (23)
  • python ^3.11
  • pydantic ^2.4.2 → [Updates: ^2.4.2]
  • injector ^0.21.0 → [Updates: ^0.24.0]
  • python-dotenv ^1.0.0 → [Updates: ^1.0.0]
  • python-dateutil ^2.8.2 → [Updates: ^2.8.2]
  • asyncpg ^0.28.0 → [Updates: ^0.32.0]
  • aiosqlite ^0.19.0 → [Updates: ^0.22.0]
  • greenlet ^3.0.0 → [Updates: ^3.0.0]
  • alembic ^1.12.0 → [Updates: ^1.12.0]
  • black ^23.10.0 → [Updates: ^24.0.0]
  • flake8 ^6.1.0 → [Updates: ^7.0.0]
  • pyproject-flake8 ^6.1.0 → [Updates: ^7.0.0]
  • mypy ^1.6.1 → [Updates: ^1.6.1, ^2.0.0]
  • pytest ^7.4.2 → [Updates: ^9.0.0]
  • pytest-env ^1.0.1 → [Updates: ^1.0.1]
  • mocker ^1.1.1
  • freezegun ^1.2.2 → [Updates: ^1.2.2]
  • pytest-asyncio ^0.21.1 → [Updates: ^0.26.0, ^1.0.0]
  • pytest-freezegun ^0.4.2
  • pytest-dotenv ^0.5.2
  • pytest-html ^4.0.2 → [Updates: ^4.0.2]
  • pytest-cov ^4.1.0 → [Updates: ^7.0.0]
  • pip-licenses ^4.3.3 → [Updates: ^4.3.3, ^5.0.0]

  • Check this box to trigger a request for Renovate to run again on this repository
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

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.

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.