fix(release): give the registry longer than two minutes to serve a new version - #24
Merged
Merged
Conversation
…w version product-engineer 0.4.0 published cleanly on 2026-09-21 and the smoke job failed anyway: six attempts over two minutes all came back ETARGET, and the version was being served minutes later. A release that worked reported red, which is the state that teaches people to stop reading the only check that looks at what a stranger installs. Fifteen attempts, twenty seconds apart, about five minutes. The budget is named once and the failure message is computed from it, because the old message spelled "six" and "two minutes" in words that nothing would have updated. Measured on the block itself, extracted from release.yml and run against a stub npx: a clean run and an update-notifier-on-stderr run both exit 0, ETARGET exits 1 after exactly fifteen attempts, and a wrong printed version still exits 1. Sade dil (teknik olmayan biri için): - Ne yapıldı: Yayın sonrası kontrol, paketin mağazada görünmesi için iki dakika yerine beş dakika bekliyor. - Ne işe yarar: Başarılı bir yayın, sırf depo biraz geç güncellendiği için "başarısız" görünmüyor; kırmızı ışık yeniden anlam taşıyor. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
product-engineer@0.4.0published cleanly on 2026-09-21 and its smoke job failed anyway: six attempts over two minutes all answeredETARGET, andnpm viewserved the version minutes later. A release that worked reported red, and a red that means nothing is how the original smoke-test defect survived in the first place.Fifteen attempts, twenty seconds apart, about five minutes. The budget is named once and the message is computed from it, because the old one spelled "six" and "two minutes" in words nothing would have updated.
Measured on the block itself, extracted from
release.ymland run against a stub npx: a clean run and a run with npm's update notifier on stderr both exit 0,ETARGETexits 1 after exactly fifteen attempts, and a wrong printed version still exits 1.