Title: The `canary` dist-tag can move back to an older build · Issue #3783 · angular/angularfire · GitHub
Open Graph Title: The `canary` dist-tag can move back to an older build · Issue #3783 · angular/angularfire
X Title: The `canary` dist-tag can move back to an older build · Issue #3783 · angular/angularfire
Description: 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 ta...
Open Graph Description: 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 ...
X Description: 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 ...
Opengraph URL: https://github.com/angular/angularfire/issues/3783
X: @github
Domain: github.com
IPv4 address: 140.82.114.4
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"The `canary` dist-tag can move back to an older build","articleBody":"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.\n\n### Details\n\n- **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.\n - 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.\n- **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.\n- **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](https://github.com/angular/angularfire/actions/runs/36650356667)). The tag stays on the older build until the next merge.\n\n### Scope\n\nI have not seen the tag move back yet. While it sits on an older build, `npm install @angular/fire@canary` installs that build.\n","author":{"url":"https://github.com/armando-navarro","@type":"Person","name":"armando-navarro"},"datePublished":"2026-10-02T18:48:44Z","url":"https://github.com/angular/angularfire/issues/3783"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:0238f88d-1f89-be8f-a706-ac3f646645dd |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B57C:32A57E:71CE35:905702:6B0369C4 |
| html-safe-nonce | c2ec6125e15aca41b2f0c6bb0857f8dd35a83e4c74457cf35e4ebbfe1a45fb8a |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCNTdDOjMyQTU3RTo3MUNFMzU6OTA1NzAyOjZCMDM2OUM0IiwidmlzaXRvcl9pZCI6Ijg4MTIyOTA4MjIxMjM5NTQ2MCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | a334b4f381dabb02d7ae0230e3feb29ed66baa349f37bff0a8ad54b234c2edf6 |
| hovercard-subject-tag | issue:5681874426 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angularfire/3783/issue_layout |
| twitter:image | https://opengraph.githubassets.com/460275f8a335f1e15301db820cf9a4ceab3bdfce1413d4f1599b74b695abd6f4/angular/angularfire/issues/3783 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/460275f8a335f1e15301db820cf9a4ceab3bdfce1413d4f1599b74b695abd6f4/angular/angularfire/issues/3783 |
| og:image:alt | 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 ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | armando-navarro |
| hostname | github.com |
| expected-hostname | github.com |
| None | 87e774ee7c6b3bee0490394e4d3e57ec9dbc956f74b87ea685dc8996c1676456 |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angularfire git https://github.com/angular/angularfire.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 49453413 |
| octolytics-dimension-repository_nwo | angular/angularfire |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 49453413 |
| octolytics-dimension-repository_network_root_nwo | angular/angularfire |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 423dbb54c5e7bfecc838eb387c1435eb3d0e760d |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
| Server | github.com |
| Content-Type | text/html; charset=utf-8 |
| Cache-Control | max-age=0, private, must-revalidate |
Viewport: width=device-width