Skip to content
Snippets Groups Projects
This project is mirrored from https://github.com/angular/angular.git. Pull mirroring updated .
  1. Mar 07, 2019
    • George Kalpakas's avatar
      build(docs-infra): use pinned dependencies when possible in `ng-packages-installer` (#28510) · 79fb9d44
      George Kalpakas authored
      Previously, `ng-packages-installer` would replace the version ranges for
      all dependencies that were peer dependencies of an Angular package with
      the version range used in the Angular package. This effectively meant
      that the pinned version (from `yarn.lock`) for that dependency was
      ignored (even if the pinned version satisfied the new version range).
      
      This commit reduces non-determinism in CI jobs using the locally built
      Angular packages by always using pinned versions of dependencies for
      Angular package peer dependencies if possible.
      
      For example, assuming the following versions for the RxJS dependency:
      
      - **aio/package.json**: `rxjs: ^6.3.0`
      - **aio/yarn.lock**: `rxjs@^6.3.0: 6.3.3`
      - **@angular/core#peerDependencies**: `rxjs: ^6.0.0`
      
      ...the following versions would be used with `ng-packages-installer`:
      
      - Before this commit:
        - **aio/package.json**: `rxjs: ^6.0.0`
        - **node_modules/rxjs/**: `6.4.0` (latest version satisfying `^6.0.0`)
      - After this commit:
        - **aio/package.json**: `rxjs: ^6.3.0`
        - **node_modules/rxjs/**: `6.3.3` (because it satisfies `^6.0.0`)
      
      PR Close #28510
      79fb9d44
    • George Kalpakas's avatar
      build(docs-infra): keep other dependencies pinned when installing local Angular packages (#28510) · 73a93d3a
      George Kalpakas authored
      `ng-packages-installer` can be used to replace Angular packages with
      locally built ones (from `dist/packages-dist/`) along with their peer
      dependencies.
      
      Previously, in order to achieve this, `yarn install` was called with the
      `--no-lockfile` option, which resulted in installing the latest versions
      of all dependencies (including transitive ones) permitted by the
      corresponding version ranges in `package.json` files. As a result, newly
      released versions would be picked, resulting in unexpected,
      non-deterministic breakages in CI.
      
      This commit calls `yarn install` with the `--pure-lockfile` option
      instead. As a result, only the Angular packages (for which the locally
      built ones are used) and their peer dependencies are unpinned; the
      pinned versions from `yarn.lock` are used for all other (direct and
      transitive) dependencies.
      
      While this does not eliminate non-determinism across builds, it
      significantly reduces it.
      
      PR Close #28510
      73a93d3a
    • George Kalpakas's avatar
    • George Kalpakas's avatar
    • George Kalpakas's avatar
      build(docs-infra): remove unnecessary workaround for RxJS in `ng-packages-installer` (#28510) · 2eb5fe69
      George Kalpakas authored
      Since b43f8bc7, RxJS does not need to be patched any more in the
      top-level `node_modules/`, so we don't need to special-case RxJS in
      `ng-package-installer` and use `node_modules/rxjs/`.
      
      PR Close #28510
      2eb5fe69
    • George Kalpakas's avatar
      ci(docs-infra): fix deployment to Firebase · f99febcd
      George Kalpakas authored
      This is a backport of f1a860fb to 6.1.x.
      Related to #29029.
      f99febcd
  2. Mar 01, 2019
  3. Oct 16, 2018
  4. Oct 14, 2018
  5. Oct 13, 2018
  6. Oct 12, 2018
  7. Oct 11, 2018
  8. Oct 09, 2018
  9. Oct 06, 2018