Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto Apto para principiantes
  • ¿Algo no está bien?
#7,925 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
92/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, shell
Área
ci-cd, release

Línea de trabajo

Comienza con .github/workflows/dependabot-fragments.yml, especialmente con los pasos de concurrencia y generación de fragmentos, y compara la ejecución en espera con el workflow release-publish-plugins.yml correcto. Cancela la ejecución 38093644200 con el comando gh o el comando de la API de GitHub documentados y, a continuación, confirma que no queda ninguna ejecución de dependabot-fragments en espera. Terminar significa que la siguiente ejecución programada o disparada por un push se completa correctamente y abre o actualiza release/dependabot-fragments, o registra que no hay fragmentos pendientes.

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

Descripción

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

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
7 h 8 min
PR fusionados (30 d)
874

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.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.