Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

fix(ci): cancel the dependabot-fragments run stuck waiting on plugin-release since 2026-10-10

Aperta Adatta ai principianti
  • Qualcosa non va?
#7,925 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
92/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, shell
Ambito
ci-cd, release

Direzione di ricerca

Inizia da .github/workflows/dependabot-fragments.yml, in particolare dai passaggi di concorrenza e generazione dei frammenti, e confronta l'esecuzione in attesa con il workflow release-publish-plugins.yml riuscito. Annulla l'esecuzione 38093644200 con il comando gh o con il comando dell'API GitHub documentato, quindi conferma che non rimanga alcuna esecuzione di dependabot-fragments in attesa. Fatto significa che la successiva esecuzione pianificata o attivata da un push riesce e apre o aggiorna release/dependabot-fragments, oppure registra che non ci sono frammenti in sospeso.

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

Descrizione

needs-human

No related issue: found by the monitoring session

Summary

One dependabot-fragments run, 38093644200 (push, 2026-10-10T23:02Z, head 786dd9a9), has sat in waiting on the plugin-release environment for seven days. It holds the workflow's concurrency group, so every later run waits behind it as pending and is cancelled when the next one arrives. 500 of the 501 runs in the last 7 days ended cancelled (330 on push, 170 scheduled), and none of them got a job (/actions/runs/39091122869/jobs is empty). The last successful run was 38092025605 on 2026-10-10T22:35Z.

Evidence:

  • .github/workflows/dependabot-fragments.yml:32-34: concurrency: group: dependabot-fragments, cancel-in-progress: false, set at the workflow level, so a run that is waiting on its environment holds the group.
  • GET /actions/runs/38093644200/pending_deployments: environment plugin-release, reviewers: [], wait_timer: 0, current_user_can_approve: false. The environment has only a branch_policy rule. There is nothing to approve, yet the run stays waiting. It is the only waiting run in the repository.
  • The same environment passes for release-publish-plugins.yml (its runs on 2026-10-18 succeed), so the environment itself does not block. The likely trigger is github-iac#633 (2026-10-10T14:55Z, "disable admin bypass on the plugin-release environment"), but that link is UNVERIFIED.
  • GitHub concurrency docs (https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency): "When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. By default, any existing pending job or workflow in the same concurrency group will be canceled and the new queued job or workflow will take its place."

Impact: no changelog fragment has been written for any Dependabot merge since 2026-10-10. The search API returns 19 merged Dependabot PRs for that window (for example #7706, #7707, #7708); the ones that touch fragment-mode plugins have no fragment, so the release PR leaves those bumps out. No runner minutes are wasted, because the cancelled runs never started a job. The cost is the missing fragments.

Fix

  1. Cancel the stuck run: gh run cancel 38093644200 -R melodic-software/claude-code-plugins, or, if it stays waiting, POST /repos/melodic-software/claude-code-plugins/actions/runs/38093644200/force-cancel. The run never reached a step, so the workflow's concern about cancelling after the force-reset (lines 28-31) does not apply. The next push or the :23 schedule then runs from main and writes every missing fragment, because fragments are named by merge commit (line 16-17).
  2. No workflow change is needed for this incident. Revisit only if a run sticks again.

Verification

  • gh api repos/melodic-software/claude-code-plugins/actions/runs?status=waiting returns no dependabot-fragments run.
  • The next dependabot-fragments run ends success, and either opens or updates release/dependabot-fragments with the missing fragments, or logs that none are pending.

Related

  • #5786 (why Dependabot PRs carry no fragment)
  • ADR 0048 (docs/adr/0048-release-plugins-from-changelog-fragments-through-a-bot-maintained-release-pr.md)

🤖 Generated with Claude Code

https://claude.ai/code/session_01PfAeL8XHnWAexMLmaSzZZH

Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
8h 41m
PR unite (30g)
892

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.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.