Title: fix(ci): keep the canary dist-tag from moving back to an older build by armando-navarro · Pull Request #3784 · angular/angularfire · GitHub
Open Graph Title: fix(ci): keep the canary dist-tag from moving back to an older build by armando-navarro · Pull Request #3784 · angular/angularfire
X Title: fix(ci): keep the canary dist-tag from moving back to an older build by armando-navarro · Pull Request #3784 · angular/angularfire
Description: Fixes #3783
The publish job now publishes a canary only when its commit comes after the commit of the canary already on npm, and canary publishes run one at a time.
Changes
All in the publish job of .github/workflows/test.yml.
New step, "Skip a canary that is not newer than npm's". It runs for canary versions only, without the npm token.
It reads the current canary from npm's dist-tags endpoint, which is not CDN-cached. The package data that npm view reads is cached for 5 minutes.
It clones the repository's commit history with git clone --bare --filter=tree:0, which takes about half a second, and finds the commit named at the end of that canary's version.
Then it decides:
This build's commit comes after that commit: publish.
Same commit and same version: skip with a notice.
Same commit under a different version: publish. This can't happen today. It will after #3780, when the scheduled run rebuilds an unchanged main after a release.
This build's commit comes before that commit: skip with a warning.
Neither commit comes before the other, or the canary's commit can't be found: fail the job.
concurrency on the job. Canary publishes share the group canary-publish with cancel-in-progress: false and queue: max, so they run one at a time and a waiting one is not replaced. Each release run gets a group of its own.
The Publish step runs unless the new step asked to skip.
Releases and release candidates publish exactly as before.
Behavior to be aware of
The weekday scheduled run stops failing. On an unchanged main its publish fails with E403 today, as it did on 2026-09-30 and 2026-10-02. It now skips with a notice.
A failed check stays failed. If the canary dist-tag is missing, or points at a build from a commit that is not on main, the step fails and so does every later canary publish. The error message says so and names the fix: someone with publish rights runs npm dist-tag add @angular/fire@
Open Graph Description: Fixes #3783 The publish job now publishes a canary only when its commit comes after the commit of the canary already on npm, and canary publishes run one at a time. Changes All in the publish job o...
X Description: Fixes #3783 The publish job now publishes a canary only when its commit comes after the commit of the canary already on npm, and canary publishes run one at a time. Changes All in the publish job o...
Opengraph URL: https://github.com/angular/angularfire/pull/3784
X: @github
Domain: github.com
IPv4 address: 140.82.112.3
| 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 | /:user_id/:repository/pull/:id/files(.:format) |
| route-controller | pull_requests |
| route-action | files |
| fetch-nonce | v2:ebeb1487-4f12-ea6a-5548-39effe7b8772 |
| current-catalog-service-hash | ae870bc5e265a340912cde392f23dad3671a0a881730ffdadd82f2f57d81641b |
| request-id | 9148:1316A2:36B1A4:489852:6B037D38 |
| html-safe-nonce | 5f087f9bf03e60bd1bf2d1b530885ed9efecea5d311f64a52d024dcb5bdffffa |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5MTQ4OjEzMTZBMjozNkIxQTQ6NDg5ODUyOjZCMDM3RDM4IiwidmlzaXRvcl9pZCI6IjcyMTg5NTQwMzkwNDI3MzU0MTYiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 0082e47693f1380a80f2fcec78e7ad8cfcffc778ceaf9c224a3fd00303d47493 |
| hovercard-subject-tag | pull_request:4720183963 |
| github-keyboard-shortcuts | repository,pull-request-list,pull-request-conversation,pull-request-files-changed,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/angular/angularfire/pull/3784/files |
| twitter:image | https://avatars.githubusercontent.com/u/13904589?s=400&v=4 |
| twitter:card | summary_large_image |
| og:image | https://avatars.githubusercontent.com/u/13904589?s=400&v=4 |
| og:image:alt | Fixes #3783 The publish job now publishes a canary only when its commit comes after the commit of the canary already on npm, and canary publishes run one at a time. Changes All in the publish job o... |
| og:site_name | GitHub |
| og:type | object |
| hostname | github.com |
| expected-hostname | github.com |
| None | 87e774ee7c6b3bee0490394e4d3e57ec9dbc956f74b87ea685dc8996c1676456 |
| turbo-cache-control | no-preview |
| diff-view | unified |
| 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 | true |
| 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 |
Links:
| Server | github.com |
| Content-Type | text/html; charset=utf-8 |
| Cache-Control | no-cache |
Viewport: width=device-width