Dependency Dashboard

Open
#109 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
github-actions, python
Domain
ci-cd, devops, tooling

Research direction

Start with the Renovate Dependency Dashboard and its linked PRs, then inspect requirements_dev.txt, pyproject.toml, and .github/workflows/codeql.yml. Review the Renovate dashboard documentation before deciding which dependency updates remain actionable; done means the relevant updates are handled and the dashboard is current.

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.

Open

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

Detected Dependencies

github-actions (1)
.github/workflows/codeql.yml (4)
  • actions/checkout v3 → [Updates: v6]
  • github/codeql-action v2 → [Updates: v4]
  • github/codeql-action v2 → [Updates: v4]
  • github/codeql-action v2 → [Updates: v4]
pep621 (1)
pyproject.toml (1)
  • setuptools >= 40.6.0
pip_requirements (1)
requirements_dev.txt (8)
  • bump2version ==1.0.1
  • coverage ==7.2.7 → [Updates: ==7.13.5]
  • pip ==23.1.2 → [Updates: ==26.0]
  • pytest ==7.3.1 → [Updates: ==9.0.3]
  • Sphinx ==7.0.1 → [Updates: ==7.4.7, ==9.1.0]
  • tox ==4.6.0 → [Updates: ==4.53.0]
  • twine ==4.0.2 → [Updates: ==6.2.0]
  • wheel ==0.40.0 → [Updates: ==0.46.2]

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

Contributor guide

Open the 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 DiamondLightSource/python-procrunner

All issues in DiamondLightSource/python-procrunner

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.