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

Recover abandoned Changesets signing helper refs before release updates

Abierto
  • ¿Algo no está bien?
#547 0 comentarios 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, node.js, typescript
Área
ci-cd, release

Línea de trabajo

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.

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

Descripción

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).

Lenguaje dominante
TypeScript
Estrellas
73
Forks
26
Merge medio
13 h 19 min
PR fusionados (30 d)
32

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 transloadit/node-sdk

Todos los issues de transloadit/node-sdk

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.