Skip to content

Commit 95b3de1

Browse files
chore: bump version to 21.0.0-rc.1 (#3751)
The publish job reads this literal at tag time. The sample's file: tarball dependency path and its README install example carry the same version, so they move together. The root lockfile records the same version in its two version fields. The sample's lockfile deliberately keeps the rc.0 tarball name, because it also records that tarball's integrity hash.
1 parent 345726a commit 95b3de1

4 files changed

Lines changed: 6 additions & 6 deletions

File tree

‎package-lock.json‎

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎package.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@angular/fire",
3-
"version": "21.0.0-rc.0",
3+
"version": "21.0.0-rc.1",
44
"description": "Angular + Firebase = ❤️",
55
"publishConfig": {
66
"registry": "https://wombat-dressing-room.appspot.com",

‎sample/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ This project was generated using [Angular CLI](https://github.com/angular/angula
44

55
## AngularFire tarball
66

7-
The sample consumes the library as `file:../angular-fire-21.0.0-rc.0.tgz`. Produce that file from the repository root before installing here:
7+
The sample consumes the library as `file:../angular-fire-21.0.0-rc.1.tgz`. Produce that file from the repository root before installing here:
88

99
```bash
1010
npm ci
@@ -16,7 +16,7 @@ The root build ends with `npm pack ./dist/packages-dist`, which writes `angular-
1616
Then, from this `sample/` folder, install the dependencies by naming the tarball explicitly:
1717

1818
```bash
19-
npm install ../angular-fire-21.0.0-rc.0.tgz
19+
npm install ../angular-fire-21.0.0-rc.1.tgz
2020
```
2121

2222
A plain `npm install` is not reliable here. `package-lock.json` records the integrity hash of the tarball built by whoever committed the lockfile, and a tarball you build yourself can hash differently. With a cold npm cache the install then fails with an `EINTEGRITY` error. With a warm cache that holds the recorded hash, npm installs the stale cached copy and exits successfully, so you would be testing a library you did not build. Naming the tarball installs the file on disk and rewrites the recorded hash in your local `package-lock.json`. Leave that lockfile change uncommitted.

‎sample/package.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
"@angular/common": "^21.0.0",
1515
"@angular/compiler": "^21.0.0",
1616
"@angular/core": "^21.0.0",
17-
"@angular/fire": "file:../angular-fire-21.0.0-rc.0.tgz",
17+
"@angular/fire": "file:../angular-fire-21.0.0-rc.1.tgz",
1818
"@angular/forms": "^21.0.0",
1919
"@angular/platform-browser": "^21.0.0",
2020
"@angular/platform-server": "^21.0.0",

0 commit comments

Comments
 (0)