Recover abandoned Changesets signing helper refs before release updates
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, node.js, typescript
调研方向
Start with the Changesets helper behavior in @changesets/ghcommit 2.1.1 src/core.ts, then inspect this repository’s Release workflow and CONTRIBUTING.md. Define a preflight or recovery path that detects the named temporary ref and verifies it is abandoned generated work before any cleanup; refuse unexpected or concurrent work. Add behavioral tests for clean, stale-ref, and refusal cases. Done means reruns explain or safely recover the failure while preserving signed commits and the review/green-CI gate.
由索引模型根据 Issue 内容生成。
描述
Updating the generated Version Packages PR can fail even though changeset-release/main is explicitly exempt from the organization's non-fast-forward rule.
Release run https://github.com/transloadit/node-sdk/actions/runs/37736494496 failed in attempts 1 and 2 while refreshing https://github.com/transloadit/node-sdk/pull/544 after the approved alphalib sync and Assembly reader corrections. GitHub reported Cannot force-push to this branch; the rule-suite record identifies the actual ref as refs/heads/changesets-ghcommit-temp/changeset-release/main.
The pinned Changesets action uses @changesets/ghcommit 2.1.1 to create signed commits. For an existing release branch, that helper creates a temporary branch and force-resets it when a prior temporary branch already exists. The organization's rule excludes refs/heads/changeset-release/*, but deliberately keeps the temporary namespace under its normal force-push protection.
The abandoned temporary ref pointed at f8d757414a8470f277b0e49b9564602dcafb3d1f, a verified github-actions[bot] Version Packages commit from July 11. Its diff contains only changeset removals, package versions, changelogs and the lockfile. No current release job was active. Its commit was fetched and preserved locally, then only this stale bot artifact was deleted before rerunning the latest main workflow. The real Version Packages branch and PR were retained, and no repository or organization rules were weakened.
Improve release preflight/recovery and CONTRIBUTING.md so a plain rerun cannot repeatedly hit this opaque error. Consider a bounded cleanup of a verified abandoned bot temporary ref under the existing serialized Release workflow, or at least emit its exact name, commit and safe operator procedure. Refuse unexpected source changes or active release work. Preserve signed commits and the human review/green-CI gate for Version Packages. Add behavioral tests for the clean path, a stale generated helper ref, and refusal to remove non-generated or concurrent work.
The source behavior is in https://github.com/changesets/ghcommit/blob/v2.1.1/src/core.ts (temporary-ref recovery in commitFilesFromBase64).
- 主要语言
- TypeScript
- 星标
- 73
- 派生
- 26
- 平均合并
- 13 小时 19 分钟
- 30 天内合并 PR
- 32
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
transloadit/node-sdk 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 35/100
transloadit/node-sdk#501 ·
维护者通常 1 天内回复
-
Enforce SHA-384 signatures in Node SDK可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 3/5 1-2 天 新手友好度 65/100
transloadit/node-sdk#400 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
transloadit/node-sdk#344 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
transloadit/node-sdk#276 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
transloadit/node-sdk#270 ·
维护者通常 1 天内回复
查看 transloadit/node-sdk 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
Agenta-AI/agenta#7542 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
code quality security
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 90/100
-
难度 1/5 1 小时以内 新手友好度 82/100
homarr-labs/dashboard-icons#2939 ·
维护者通常 1 天内回复