Dependency Dashboard

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

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
12/100
Tipo di issue
Refactoring
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
docker, github-actions, go
Ambito
ci-cd

Direzione di ricerca

This is a Renovate Dependency Dashboard, a bot-maintained tracking issue rather than a task. The pending updates touch .github/workflows/ci.yml, .github/workflows/release.yml, go.mod and .mise.toml. Work here means ticking a checkbox to create a Renovate PR, which a maintainer should decide, so there is no clear first step for a newcomer.

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.

Awaiting Schedule

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

  • chore(deps): lock file maintenance
  • chore(deps): update actions/checkout action to v7
  • chore(deps): update jdx/mise-action action to v5
  • 🔐 Create all awaiting schedule PRs at once 🔐

Pending Status Checks

The following updates await pending status checks. To force their creation now, click on a checkbox below.

  • chore(deps): update dependency go to v1.27.4

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 (3)
  • docker/dockerfile 1@sha256:4edf897a3ffa55b89f906fc8cc78afdb3f1834cc9c7083565e611a8a7d5fe99e
  • golang 1.27-trixie@sha256:f18c3d73a184fb0582828510722e723b63a93f7188d11dd223d9be6f6880e65d
  • debian trixie-slim@sha256:a72b4433de1cf7d6bae0c4cee74d0547f58601a643b3375f070c51600d63b6b2
github-actions (2)
.github/workflows/ci.yml (5)
  • actions/checkout v6@d23441a48e516b6c34aea4fa41551a30e30af803 → [Updates: v7]
  • jdx/mise-action v4@c2a87611a18de5b3828c5652fe268e992400cb5c → [Updates: v5]
  • actions/checkout v6@d23441a48e516b6c34aea4fa41551a30e30af803 → [Updates: v7]
  • docker/setup-buildx-action v4@37fe631027851001ddb9b187196cc803df7f5f0e → [Updates: v4]
  • docker/build-push-action v7.4.0@c3c9e263c25d99ce0380d002d59b67737d91b0dc
.github/workflows/release.yml (6)
  • actions/checkout v6@d23441a48e516b6c34aea4fa41551a30e30af803 → [Updates: v7]
  • docker/setup-qemu-action v4@99012661954931238ded8c8b007157a8430204e1
  • docker/setup-buildx-action v4@37fe631027851001ddb9b187196cc803df7f5f0e → [Updates: v4]
  • docker/login-action v4@8aa5831fb8d48d8f76594c7ddde61ae58019f550
  • docker/metadata-action v6@dc802804100637a589fabce1cb79ff13a1411302
  • docker/build-push-action v7.4.0@c3c9e263c25d99ce0380d002d59b67737d91b0dc
gomod (1)
go.mod (2)
  • go 1.27.0
  • github.com/prometheus/client_golang v1.25.0
mise (1)
.mise.toml (1)
  • go 1.27.3 → [Updates: 1.27.4]
Lingua principale
Go
Stelle
0
Fork
1
Merge medio
4h 33m
PR unite (30g)
7

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 Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.