mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
8d8cdc1991
Previously, the master branch was only deployed to the `next-angular-io-site` Firebase site, which is connected to the `next.angular.io` domain. However, if the master major version was higher than the stable major version (or the RC major version in case there was an active RC), we also had to manually configure (via the Firebase console and/or DNS records) the `v<X>.angular.io` domain to redirect to `next.angular.io`. Then, once `<X>` became the new stable or RC version, we had to manually remove the redirect (to let `v<X>.angular.io` be redirected to `angular.io` or `rc.angular.io`). This commit is part of a new process that reduces the manual steps as follows (the steps below only apply when the master major version is higher than the current stable and RC (if applicable)): - A `v<X>-angular-io-site` Firebase site will be created as soon as the version in the `master` branch's `package.json` is updated to a new major. - The `v<X>.angular.io` domain will be connected to that new Firebase site. - When deploying from the master branch, we will deploy to both `next-angular-io-site` and `v<X>-angular-io-site`. In addition, the deployment to `v<X>-angular-io-site` will update the Firebase config file to redirect to `next.angular.io`. - When the master version becomes the new stable/RC, we will start deploying to `v<X>-angular-io-site` from the stable/RC branch, which will update the Firebase config to stop redirecting to `next.angular.io` and redirect to `(rc.)angular.io` instead (without requiring changes in the Firebase console or DNS). PR Close #43963 |
||
|---|---|---|
| .. | ||
| contributors | ||
| deploy-to-firebase | ||
| audit-web-app.mjs | ||
| build-404-page.js | ||
| build-artifacts.sh | ||
| build-ngsw-config.js | ||
| check-environment.js | ||
| create-preview.js | ||
| payload.sh | ||
| test-aio-a11y.mjs | ||
| test-external-urls.js | ||
| test-preview.js | ||
| test-production.sh | ||