Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

The `canary` dist-tag can move back to an older build

Fechada
  • Algo errado?
#3,783 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
52/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github-actions, node.js
Domínio
ci-cd, devops, release

Direção de pesquisa

Start by inspecting the GitHub Actions workflow's canary build and publish job, especially the npm publish --tag canary step and the weekday scheduled run. Trace how concurrent and re-run jobs select the commit to publish; done means an older build cannot move the canary tag backward and the scheduled run can restore the latest canary without the reported E403 failure.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Every push to main and every weekday scheduled run builds a canary and runs npm publish --tag canary, which moves the canary dist-tag to that build. Nothing checks that the build is newer than the one the tag already points at, so the tag can end up on an older build.

Details
  • Two merges close together can publish out of order. Each merge starts its own workflow run, and the publish job waits for that run's tests. If a second merge lands while the first run is still going and the first run's tests finish last, the older commit's canary publishes last and takes the tag.
    • A run takes about 6 to 7 minutes. On 2026-09-27 the run for f182972 started 21 seconds after the canary for 84a8a51 had published.
  • Re-running an older run can publish it late. A run on main whose canary never published, for example because a test failed, publishes when it is re-run, even if newer canaries have gone out since.
  • Nothing puts the tag back. The weekday scheduled run rebuilds the latest commit on main, whose version is already on npm, so its publish fails with E403 (example). The tag stays on the older build until the next merge.
Scope

I have not seen the tag move back yet. While it sits on an older build, npm install @angular/fire@canary installs that build.

Linguagem predominante
TypeScript
Estrelas
7.8k
Forks
2.2k
Merge médio
3d 2h
PRs com merge (30d)
13

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de angular/angularfire

Todas as issues de angular/angularfire

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.