Dependency Dashboard

Abierto
#4 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
1/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
docker, github-actions, shell

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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]
Lenguaje dominante
Shell
Estrellas
0
Forks
1
Merge medio
24 min
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.