Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Dependency Dashboard

Ouverte
#1 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
10/100
Type d'issue
Refactorisation
Clarté
À clarifier
Activité
À l'abandon
Stack technique
dockerfile, github-actions

Piste de recherche

Start with the Dependency Dashboard, Dockerfile, .github/workflows/build.yml, and renovate.json. Review the existing update pull requests 1037–1044 and the branch-specific image updates, then determine whether any checkbox action still needs to be triggered. Done means the listed dependency updates have been handled and the dashboard no longer requires those actions.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

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.

Open

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

Detected Dependencies

Branch main
dockerfile (1)
Dockerfile (2)
  • ghcr.io/vexxhost/openstack-venv-builder main@sha256:9552e59ecae968b93f798e23ef85005454a2cf44ad7b699688f8198efc15d377 → [Updates: main]
  • ghcr.io/vexxhost/python-base main@sha256:f42d87d0d471ab52c9ca66efa9d976911ac516f8ce7f0734a91fe249db834658 → [Updates: main]
github-actions (1)
.github/workflows/build.yml (2)
  • step-security/harden-runner v2.21.1@e14015d583714f6e62063499dc959a02595150a1
  • vexxhost/docker-atmosphere main@d048c9245c93c10c06d42d1ea9311fcd3d416530
renovate-config (1)
renovate.json
Branch stable/2023.1
dockerfile (1)
Dockerfile (2)
  • ghcr.io/vexxhost/openstack-venv-builder 2023.1@sha256:3ab324e59a6ea02f9b39ecb30b000d07b702685b332d56a4e69f0c485f460621 → [Updates: 2023.2, 2026.1]
  • ghcr.io/vexxhost/python-base 2023.1@sha256:0415df140f6a1174aee86810176c2ca1c0c05f29280249b8c84e9e4e61553533 → [Updates: 2023.2, 2026.1]
github-actions (1)
.github/workflows/build.yml (1)
  • vexxhost/docker-atmosphere main@d048c9245c93c10c06d42d1ea9311fcd3d416530
renovate-config (1)
renovate.json
Branch stable/2023.2
dockerfile (1)
Dockerfile (2)
  • ghcr.io/vexxhost/openstack-venv-builder 2023.2@sha256:314caa73de380a07b83dd22e9d2335e62ca2017f925a947a1d44f096a7a309c1 → [Updates: 2026.1, 2023.2]
  • ghcr.io/vexxhost/python-base 2023.2@sha256:23a15ee6a54e2f0ae9949d04ed6b8cdd5177742312db3abfb55689b56528709e → [Updates: 2026.1, 2023.2]
github-actions (1)
.github/workflows/build.yml (1)
  • vexxhost/docker-atmosphere main@d048c9245c93c10c06d42d1ea9311fcd3d416530
renovate-config (1)
renovate.json
Branch stable/2024.1
dockerfile (1)
Dockerfile (2)
  • ghcr.io/vexxhost/openstack-venv-builder 2024.1@sha256:e4e3d1ba79c1ba43d1d5afea8e882ff04ab250ad51e26b303f12e152b76a4514 → [Updates: 2024.2, 2026.1, 2024.1]
  • ghcr.io/vexxhost/python-base 2024.1@sha256:db167f4694d0b1502faf727e667587c54250d5b0a262eca0899709ac7d628021 → [Updates: 2024.2, 2026.1, 2024.1]
github-actions (1)
.github/workflows/build.yml (1)
  • vexxhost/docker-atmosphere main@d048c9245c93c10c06d42d1ea9311fcd3d416530
renovate-config (1)
renovate.json
Branch stable/2024.2
dockerfile (1)
Dockerfile (2)
  • ghcr.io/vexxhost/openstack-venv-builder 2024.2@sha256:5f8bfdef9a688fef228b7889964a750dbe2e145e7baaed3390c3c877b3cdb367 → [Updates: 2026.1, 2024.2]
  • ghcr.io/vexxhost/python-base 2024.2@sha256:6b648645949598427fc044ac85cb364de1c0a89662e48a5ef0d30b8ed2b3976d → [Updates: 2026.1, 2024.2]
github-actions (1)
.github/workflows/build.yml (1)
  • vexxhost/docker-atmosphere main@d048c9245c93c10c06d42d1ea9311fcd3d416530
renovate-config (1)
renovate.json
Branch stable/2025.1
dockerfile (1)
Dockerfile (2)
  • ghcr.io/vexxhost/openstack-venv-builder 2025.1@sha256:c8fce46ccda5251f5c59006603cc0594599b2d73b65eabbc8d73bec103846541 → [Updates: 2025.2, 2026.1, 2025.1]
  • ghcr.io/vexxhost/python-base 2025.1@sha256:aa2dc02c5662a08071a27d11ecc1bc9d9690c68c6006caa48c18fb9501818bc3 → [Updates: 2025.2, 2026.1, 2025.1]
github-actions (1)
.github/workflows/build.yml (1)
  • vexxhost/docker-atmosphere main@d048c9245c93c10c06d42d1ea9311fcd3d416530
renovate-config (1)
renovate.json
Branch stable/2025.2
dockerfile (1)
Dockerfile (2)
  • ghcr.io/vexxhost/openstack-venv-builder 2025.2@sha256:5528f59558327af1bfd74b440ddeeb112f5163ba234007e27fab82037da41192 → [Updates: 2026.1, 2025.2]
  • ghcr.io/vexxhost/python-base 2025.2@sha256:801cce0233d690935d16d89a0c0a688eacb3368b243146bd5582fbf3f7156e42 → [Updates: 2026.1, 2025.2]
github-actions (1)
.github/workflows/build.yml (1)
  • vexxhost/docker-atmosphere main@d048c9245c93c10c06d42d1ea9311fcd3d416530
renovate-config (1)
renovate.json
Branch stable/2026.1
dockerfile (1)
Dockerfile (2)
  • ghcr.io/vexxhost/openstack-venv-builder 2026.1@sha256:0d814b5e8fbeb107f44d0597672084acee1fb90f6e0bf3720d5e27453e92ed15 → [Updates: 2026.1]
  • ghcr.io/vexxhost/python-base 2026.1@sha256:0a7e95f9fa54ee2451a5708fb5b2bc3eeca272bed620e4b8339ff2bbea6340ce → [Updates: 2026.1]
github-actions (1)
.github/workflows/build.yml (2)
  • step-security/harden-runner v2.21.1@e14015d583714f6e62063499dc959a02595150a1
  • vexxhost/docker-atmosphere main@d048c9245c93c10c06d42d1ea9311fcd3d416530
renovate-config (1)
renovate.json
Branch stable/zed
dockerfile (1)
Dockerfile (2)
  • ghcr.io/vexxhost/openstack-venv-builder zed@sha256:35e9cf8869d8a45b00d84b53ae1fc531a9ad93a6286e720b6e19989ef684c6fd → [Updates: zed]
  • ghcr.io/vexxhost/python-base zed@sha256:c850cf3baac7072a5e1ee1fb5dc6ca84cf9ed56b4f33331bef3907e5bcc87619 → [Updates: zed]
github-actions (1)
.github/workflows/build.yml (1)
  • vexxhost/docker-atmosphere main@d048c9245c93c10c06d42d1ea9311fcd3d416530
renovate-config (1)
renovate.json

  • Check this box to trigger a request for Renovate to run again on this repository
Langage dominant
Dockerfile
Étoiles
0
Forks
1
Merge moyen
1 min
PR mergées (30 j)
44

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Issues similaires

Plus d'issues Build System

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.