Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Recover abandoned Changesets signing helper refs before release updates

オープン
  • 何か問題がありますか？
#547 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github-actions, node.js, typescript
領域
ci-cd, release

調査の方向性

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分
マージ済み PR（30日）
32

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

transloadit/node-sdk のほかの issue

transloadit/node-sdk の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。