Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭 适合新手
  • 哪里不对？
#7,925 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
92/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, shell
领域
ci-cd, release

调研方向

从 .github/workflows/dependabot-fragments.yml 开始，重点关注并发控制和 fragment 生成步骤，并将等待中的运行与成功的 release-publish-plugins.yml workflow 进行比较。使用文档中的 gh 命令或 GitHub API 命令取消运行 38093644200，然后确认没有 dependabot-fragments 运行仍在等待。完成是指下一次定时或 push 触发的运行成功，并打开或更新 release/dependabot-fragments，或者记录没有待处理的 fragment。

由索引模型根据 Issue 内容生成。

描述

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

主要语言
Shell
星标
22
派生
2
平均合并
7 小时 8 分钟
30 天内合并 PR
874

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

melodic-software/claude-code-plugins 的其他 Issue

查看 melodic-software/claude-code-plugins 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。