Dependency Dashboard

Aperta
#4 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
1/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
docker, github-actions, shell

Direzione di ricerca

This is an automated Renovate dashboard, not a scoped change request. Start with the linked Dependency Dashboard documentation and inspect .github/workflows/publish.yml, .github/workflows/verify.yml, and the Dockerfile to understand the listed updates. Several dependency update pull requests are already open; there is no single completion criterion in this issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository Problems

Renovate tried to run on this repository, but found these problems.

  • ⚠️ WARN: Some release(s) did not have a releaseTimestamp, but as we're running with minimumReleaseAgeBehaviour=timestamp-optional, proceeding. See debug logs for more information
  • ⚠️ WARN: Some upgrade(s) did not have a releaseTimestamp, but as we're running with minimumReleaseAgeBehaviour=timestamp-optional, proceeding. See debug logs for more information

Awaiting Schedule

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

  • chore(deps): update docker/metadata-action action to v6
  • chore(deps): update docker/setup-buildx-action action to v4
  • chore(deps): update docker/setup-qemu-action action to v4
  • 🔐 Create all awaiting schedule PRs at once 🔐

Open

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

Vulnerabilities

Renovate has not found any CVEs on osv.dev.

Detected Dependencies

dockerfile (1)
dockerfile (1)
  • ollama/ollama 0.17.7@sha256:0ff452f6a4c3c5bb4ab063a1db190b261d5834741a519189ed5301d50e4434d1 → [Updates: 0.40.16]
github-actions (2)
.github/workflows/publish.yml (6)
  • actions/checkout v4 → [Updates: v7, v4]
  • docker/setup-qemu-action v3 → [Updates: v4, v3]
  • docker/setup-buildx-action v3 → [Updates: v4, v3]
  • docker/login-action v3 → [Updates: v4, v3]
  • docker/metadata-action v5 → [Updates: v6, v5]
  • docker/build-push-action v6 → [Updates: v7, v6]
.github/workflows/verify.yml (6)
  • actions/checkout v4 → [Updates: v7, v4]
  • docker/setup-qemu-action v3 → [Updates: v4, v3]
  • docker/setup-buildx-action v3 → [Updates: v4, v3]
  • docker/metadata-action v5 → [Updates: v6, v5]
  • docker/build-push-action v6 → [Updates: v7, v6]
  • actions/checkout v4 → [Updates: v7, v4]
Lingua principale
Shell
Stelle
0
Fork
1
Merge medio
24m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.