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

A canary published right after another can read a stale `canary` tag

Abierto
  • ¿Algo no está bien?
#3,791 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

@armando-navarro ya está trabajando en esto.

Desde el 8/10/2026.

  • #3794 de @armando-navarro — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
65/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, typescript
Área
release

Línea de trabajo

Look at the publish job in the CI workflow and the script that checks the canary tag before publishing (introduced in #3784). The fix should prevent the race condition where a pending canary publish is invisible during npm's malware scan. Verify by simulating two rapid canary publishes and checking that the dist-tag points to the newer version.

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

Descripción

comp: build/pipeline type: bug version: current (v17+)

#3784 made the publish job skip a canary whose commit is not after the commit of the canary already on npm. npm makes a new version, and the dist-tag the publish moved, visible only when its publish-time malware scan finishes, so that check can read a canary that is about to change.

Details
  • Over the eight canaries published since 2026-09-27, npm listed each version 56 to 249 seconds after the Publish step finished (median 127). GitHub's changelog calls the delay "typically around five minutes".
  • If two merges land close together and the older commit's publish starts inside that window, it reads the previous canary, passes the check, publishes, and leaves canary on the older build until the next merge.
Scope
  • Only the canary dist-tag is affected, so only npm install @angular/fire@canary and ng add @angular/fire@canary. latest and next move only on tagged releases.
  • It needs two merges to main within a few minutes of each other, with the older one's publish running second.
  • It lasts until the next merge publishes a newer canary.
Lenguaje dominante
TypeScript
Estrellas
7.8k
Forks
2.2k
Merge medio
3 d 2 h
PR fusionados (30 d)
13

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 angular/angularfire

Todos los issues de angular/angularfire

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.