Canary builds are ordered by commit hash, not by time, and an all-digit hash loses its leading zero
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 68/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- shell
- 領域
- build-system, release
研究方向
Start with tools/build.sh and trace how the canary version is assembled and passed to npm version. Check the resulting names and their ordering for hashes containing letters, all-digit hashes, and leading-zero hashes. Done means canary identifiers preserve the full short hash and publish in chronological version order without changing the stated 21-line release behavior.
由索引模型根據 Issue 內容生成。
描述
tools/build.sh names each canary build <version>-canary.<short sha>. That causes two problems.
Details
- npm orders canaries by their hash, not their age. A short sha containing a letter is compared as text, so the order is alphabetical.
21.0.0-rc.0-canary.345726a, published 2026-09-21, ranks below21.0.0-rc.0-canary.fb6796b, published 2026-08-20.- A short sha made only of digits is compared as a number, which ranks below every hash containing a letter. 11 published canaries have one.
- An all-digit hash that starts with 0 loses the zero.
npm versionrewrites21.0.0-canary.0123456to21.0.0-canary.123456, so the published name no longer matches the commit.
Scope
The order matters only when a version range matches canaries and nothing ranks above them, which is before a version's first release candidate. On the 21 line, the release candidates and the canaries named after them outrank every 21.0.0-canary.*, so this changes no install there.
- 主要語言
- TypeScript
- 星號
- 7.8k
- 分支
- 2.2k
- 平均合併
- 2 天 21 小時
- 30 天內合併 PR
- 7
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
angular/angularfire 的其他 Issue
-
comp: schematics type: bug version: current (v17+)
難度 3/5 1-2 天 新手友好度 76/100
angular/angularfire#3768 · 1 則留言 ·
維護者通常 1 天內回覆
-
Use `TransferState` to hand server-rendered Firestore data to the browser, instead of reading every document twice可能已有人在做 @armando-navarro 於 27 天前認領。 未關閉comp: firestore comp: ssr priority: P0 (critical) type: feature version: current (v17+)
angular/angularfire#3757 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Six `firebase` entry points have no `@angular/fire` equivalent, so their exports are unreachable可能已有人在做 @armando-navarro 於 27 天前認領。 未關閉comp: core type: feature
angular/angularfire#3755 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
comp: auth comp: ssr comp: zones type: bug version: current (v17+)
難度 3/5 1-2 天 新手友好度 76/100
angular/angularfire#3748 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 35/100
angular/angularfire#3737 · 2 則留言 · 22 個 reaction ·
維護者通常 1 天內回覆
查看 angular/angularfire 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
melgarafael/DeskcommCRM#1812 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 84/100
prisma/prisma-cli#309 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
gregwebs/pi-quota-dispatcher#26 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
openwatersio/slackwater.xyz#124 ·
維護者通常 1 天內回覆
-
agent-reported area/browser area/docs documentation good first issue hacktoberfest help wanted P2
難度 1/5 1 小時以內 新手友好度 90/100
維護者通常 2 天內回覆