Skip to content

build: update all non-major dependencies #31089

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

build: update all non-major dependencies #31089

wants to merge 1 commit into from

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented May 12, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
@bazel/bazelisk devDependencies minor 1.12.1 -> 1.26.0
@firebase/app-types (source) devDependencies minor ^0.7.0 -> ^0.9.0
@octokit/rest devDependencies minor 18.3.5 -> 18.12.0
@types/jasmine (source) devDependencies patch 5.1.7 -> 5.1.8
@types/node (source) devDependencies minor 22.14.0 -> 22.15.21
@types/selenium-webdriver (source) devDependencies patch 3.0.19 -> 3.0.26
@types/shelljs (source) devDependencies patch 0.8.15 -> 0.8.16
actions/upload-artifact action minor v4.3.1 -> v4.6.2
actions/upload-artifact action minor v4.3.6 -> v4.6.2
dgeni-packages devDependencies minor ^0.29.5 -> ^0.30.0
esbuild devDependencies minor ^0.17.5 -> ^0.25.0
jasmine (source) devDependencies minor 5.6.0 -> 5.7.1
jasmine-core (source) devDependencies minor 5.6.0 -> 5.7.1
jasmine-core (source) devDependencies minor ~5.6.0 -> ~5.7.0
jasmine-core (source) devDependencies minor ~3.10.0 -> ~3.99.0
karma (source) devDependencies minor ~6.3.0 -> ~6.4.0
karma-chrome-launcher devDependencies minor ~3.1.0 -> ~3.2.0
karma-coverage devDependencies minor ~2.0.3 -> ~2.2.0
karma-coverage devDependencies minor ~2.1.0 -> ~2.2.0
karma-sourcemap-loader devDependencies minor ^0.3.8 -> ^0.4.0
lighthouse devDependencies minor ~11.0.0 -> ~11.7.0
lighthouse-logger devDependencies minor ~1.2.0 -> ~1.4.0
reflect-metadata (source) devDependencies minor ^0.1.13 -> ^0.2.0
rollup-plugin-sourcemaps2 devDependencies patch 0.5.0 -> 0.5.2
rxjs (source) dependencies minor ~7.4.0 -> ~7.8.0
sass devDependencies minor 1.86.3 -> 1.89.0
send devDependencies minor ^0.17.2 -> ^0.19.0
shelljs devDependencies minor ^0.8.5 -> ^0.10.0
shelljs devDependencies minor ^0.8.4 -> ^0.10.0
slackapi/slack-github-action action digest 47b1876 -> f234e85
tsec devDependencies patch 0.2.2 -> 0.2.8
tsickle devDependencies minor 0.39.1 -> 0.46.3

Release Notes

bazelbuild/bazelisk (@​bazel/bazelisk)

v1.26.0

Compare Source

Bazelisk v1.26.0 comes with several improvements:

New Features (Go)

Bug Fixes & Improvements (Go)

We’d like to thank our amazing contributors @​albertocavalcante, @​bduffany, @​fmeum and @​tats-u!

v1.25.0

Compare Source

Bazelisk v1.25.0 comes with several improvements:

New Features (Python)

Bug Fixes & Improvements (Go)

We’d like to thank our amazing contributors @​hauserx, @​jwnimmer-tri and @​shs96c!

v1.24.1

Compare Source

Bazelisk v1.24.1 is a patch release with some minor fixes:

Bug Fixes & Improvements

We’d like to thank our amazing users & contributors!

v1.24.0

Compare Source

Bazelisk v1.24.0 comes with a new feature:

New Features (Go)

  • Implemented support for a new wildcard version identifier: Users may now specify a version like 7.* that refers to the latest release or candidate from the given LTS track. Please note that this is different from the existing 7.x identifier which only matches releases, but not candidates (https://github.com/bazelbuild/bazelisk/pull/636).

We’d like to thank our amazing users & contributors!

Known issue: https://github.com/bazelbuild/bazelisk/issues/640

v1.23.0

Compare Source

Bazelisk v1.23.0 comes with several improvements related to downloads:

Bug Fixes & Improvements

We’d like to thank our amazing contributors @​jjmaestro and @​jwnimmer-tri!

v1.22.1

Compare Source

Bazelisk v1.22.1 is a patch release with the following changes:

Bug Fixes & Improvements

We’d like to thank our amazing contributor @​sushain97!

v1.22.0

Compare Source

Bazelisk v1.22.0 comes with several significant changes:

New Features (Go)

Removed Features (Go)

  • Removed support for last_downstream_green since the downstream pipeline stopped producing green commits some time ago.

Bug Fixes & Improvements

We’d like to thank our amazing contributors @​fmeum and @​jwnimmer-tri!

v1.21.0

Compare Source

Bazelisk v1.21.0 comes with several significant changes:

New Features (Go)

Bug Fixes & Improvements

We’d like to thank our amazing contributors @​albertocavalcante, @​API92, @​jwnimmer-tri, @​keith and @​mzapotoczny!

v1.19.0

Compare Source

Bazelisk v1.19.0 comes with two significant changes:

We’d like to thank our amazing contributors @​crncnnr and @​katre!

v1.18.0

Compare Source

Bazelisk v1.18.0 contains some bug fixes and internal cleanups. Most notably, it uses consistent Bazel paths to avoid spurious rebuilds when downloading the same Bazel binary from a different mirror (https://github.com/bazelbuild/bazelisk/pull/465).

We’d like to thank our amazing contributors @​alexeagle, @​fmeum, @​illicitonion, @​sluongng and @​wisechengyi!

firebase/firebase-js-sdk (@​firebase/app-types)

v0.9.3

Compare Source

Patch Changes

v0.9.2

Compare Source

Patch Changes

v0.9.1

Compare Source

Patch Changes
  • 0c5150106 #​8079 - Update repository.url field in all package.json files to NPM's preferred format.

v0.9.0

Compare Source

Minor Changes

v0.8.1

Compare Source

Patch Changes

v0.8.0

Compare Source

Minor Changes
  • fdd4ab464 #​6526 - Add functionality to auto-initialize project config and emulator settings from global defaults provided by framework tooling.
octokit/rest.js (@​octokit/rest)

v18.12.0

Compare Source

Features
  • .actions.downloadWorkflowRunAttemptLogs(), .actions.getWorkflowRunAttempt(), .repos.generateReleaseNotes(), .checks.rerequestRun(). Graduate nebula, zzzax, switcheroo, baptiste previews. Removes defunkt /repos/{owner}/{repo}/actions/runs/{run_id}/retry endpoint. Renames methods to have consistent AuthenticatedUser() suffix, deprecates previous method names (#​125) (4daa9f3)

v18.11.4

Compare Source

Bug Fixes
  • removes defunkt endpoints: GET /repos/{owner}/{repo}/community/code_of_conduct, DELETE /reactions/{reaction_id}. encrypted_value and key_id parameters are required for .rest.actions.{createOrUpdateEnvironmentSecret,setSelectedReposForOrgSecret}(). access_token parameter is required for .rest.apps.deleteAuthorization(). Previews graduated: ant-man, flash, scarlet-witch, squirrel-girl (#​122) (9c02e7d)

v18.11.3

Compare Source

Bug Fixes
  • deps: bump minimal version of @octokit/plugin-paginate-rest to v2.16.4 to prevent typescript compile errors (#​120) (fca1907)

v18.11.2

Compare Source

Bug Fixes

v18.11.1

Compare Source

Bug Fixes
  • typescript: graduate previews dorian, inertia, london, lydian, wyandotte (#​116) (f1e2416)

v18.11.0

Compare Source

Features
  • octokit.rest.repos.{enable,disable}LfsForRepo(), octokit.rest.repos.mergeUpstream({ owner, repo, branch }) (916a8bb)

v18.10.0

Compare Source

Features
  • typescript: .packages.deletePackageForUser(), .packages.deletePackageVersionForUser(), .packages.restorePackageForUser(), .packages.restorePackageVersionForUser(), .secretScanning.listAlertsForOrg() (#​105) (40aeaff)
Bug Fixes
  • typescript: fix type for labels parameter in .issues.{add,set}Labels() (#​105) (40aeaff)

v18.9.1

Compare Source

Bug Fixes

v18.9.0

Compare Source

Features
  • typescript: allow_auto_merge parameter when creating / updating a repository. Search: owner in repository items may no longer be null (#​95) (c26c4fe)

v18.8.0

Compare Source

Features
  • .rest.repos.createAutolink(), .rest.repos.listAutolinks(), .rest.repos.getAutolink(), .rest.repos.deleteAutolink() (#​94) (13df9e7)

v18.7.2

Compare Source

Bug Fixes
  • typescript: .rest.repos.getRelease() response data now includes mentions_count (#​92) (01ba88f)

v18.7.1

Compare Source

Bug Fixes
  • typescript: .rest.repos.uploadReleaseAsset() requires name parameter. .head.repo property is optional in pull request response type (#​90) (515ed87)

v18.7.0

Compare Source

Features
  • typescript: add created parameter to octokit.actions.listWorkflowRuns() and octokit.actions.listWorkflowRunsForRepo() (#​89) (bd3b6a9)

v18.6.8

Compare Source

Bug Fixes

v18.6.7

Compare Source

Bug Fixes
  • typescript: octokit.rest.codeScanning.updateAlert() and octokit.rest.codeScanning.getAlert() response types no longer includes .rule.security_severity_level - reverts v18.6.6 (#​80) (91ffcf2)

v18.6.6

Compare Source

Bug Fixes
  • typescript: octokit.rest.codeScanning.updateAlert() and octokit.rest.codeScanning.getAlert() response types now include .rule.security_severity_level (#​79) (f69f2b2)

v18.6.5

Compare Source

Bug Fixes

v18.6.4

Compare Source

Bug Fixes
  • typescript: .security_and_analysis.secret_scanning property in repository responses (#​77) (36373fe)

v18.6.3

Compare Source

Bug Fixes

v18.6.2

Compare Source

Bug Fixes

v18.6.1

Compare Source

Bug Fixes
  • typescript: many type improvements via @octokit/plugin-rest-endpoint-methods v5.3.2 (#​71) (127e0a8)

v18.6.0

Compare Source

Features

v18.5.6

Compare Source

Bug Fixes

v18.5.5

Compare Source

Bug Fixes

v18.5.4

Compare Source

(that should have been a feature release, sorry)

Features
  • octokit.rest.repos.getPagesHealthCheck()
  • codeScanning.listAlertInstances(), actions.approveWorkflowRun()
  • apps.createContentAttachmentForRepo(), reactions.createForRelease(), repos.compareCommitsWithBasehead()
Deprecations
  • codeScanning.listAlertsInstances()
Bug Fixes
  • POST /repos/{owner}/{repo}/deployments (repos/create-deployment) does not accept a created_at parameter

v18.5.3

Compare Source

Bug Fixes
  • remove legacy org and organization parameters from octokit.repos.createFork() again (#​46) (8263ce9)

v18.5.2

Compare Source

Bug Fixes

v18.5.1

Compare Source

Bug Fixes

v18.5.0

Compare Source

Features
  • set all REST API endpoint methods on octokit.rest.*. The methods are also set on octokit.* for foreseeable time, but no longer documented, and will be deprecated at some point in future (#​2054) (40ee966)

v18.4.0

Compare Source

Features
  • octokit.repos.getReadmeInDirectory()
  • octokit.packages.getAllPackageVersionsForPackageOwnedByAuthenticatedUser() (deprecates octokit.packages.getAllPackageVersionsForAPackageOwnedByTheAuthenticatedUser())
  • octokit.packages.getAllPackageVersionsForPackageOwnedByOrg() (deprecates octokit.packages.getAllPackageVersionsForAPackageOwnedByAnOrg)

(#​2053) (5350388)

actions/upload-artifact (actions/upload-artifact)

v4.6.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/upload-artifact@v4...v4.6.2

v4.6.1

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.6.1

v4.6.0

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.6.0

v4.5.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/upload-artifact@v4.4.3...v4.5.0

v4.4.3

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.4.2...v4.4.3

v4.4.2

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.4.1...v4.4.2

v4.4.1

Compare Source

What's Changed
New Contributors

Full Changelog: actions/upload-artifact@v4.4.0...v4.4.1

v4.4.0

Compare Source

Notice: Breaking Changes ⚠️

We will no longer include hidden files and folders by default in the upload-artifact action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, include-hidden-files, to continue to do so.

See "Notice of upcoming deprecations and breaking changes in GitHub Actions runners" changelog and this issue for more details.

What's Changed

Full Changelog: actions/upload-artifact@v4.3.6...v4.4.0

v4.3.6

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.3.6

v4.3.5

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.4...v4.3.5

v4.3.4

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.3...v4.3.4

v4.3.3

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.2...v4.3.3

v4.3.2

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4.3.1...v4.3.2

angular/dgeni-packages (dgeni-packages)

v0.30.0

Compare Source

Features
  • default to git binary in environment variable (acb4f75)
evanw/esbuild (esbuild)

v0.25.4

Compare Source

  • Add simple support for CORS to esbuild's development server (#​4125)

    Starting with version 0.25.0, esbuild's development server is no longer configured to serve cross-origin requests. This was a deliberate change to prevent any website you visit from accessing your running esbuild development server. However, this change prevented (by design) certain use cases such as "debugging in production" by having your production website load code from localhost where the esbuild development server is running.

    To enable this use case, esbuild is adding a feature to allow Cross-Origin Resource Sharing (a.k.a. CORS) for simple requests. Specifically, passing your origin to the new cors option will now set the Access-Control-Allow-Origin response header when the request has a matching Origin header. Note that this currently only works for requests that don't send a preflight OPTIONS request, as esbuild's development server doesn't currently support OPTIONS requests.

    Some examples:

    • CLI:

      esbuild --servedir=. --cors-origin=https://example.com

    • JS:

      const ctx = await esbuild.context({})
await ctx.serve({
  servedir: '.',
  cors: {
    origin: 'https://example.com',
  },
})

    • Go:

      ctx, _ := api.Context(api.BuildOptions{})
ctx.Serve(api.ServeOptions{
  Servedir: ".",
  CORS: api.CORSOptions{
    Origin: []string{"https://example.com"},
  },
})

    The special origin * can be used to allow any origin to access esbuild's development server. Note that this means any website you visit will be able to read everything served by esbuild.

  • Pass through invalid URLs in source maps unmodified (#​4169)

    This fixes a regression in version 0.25.0 where sources in source maps that form invalid URLs were not being passed through to the output. Version 0.25.0 changed the interpretation of sources from file paths to URLs, which means that URL parsing can now fail. Previously URLs that couldn't be parsed were replaced with the empty string. With this release, invalid URLs in sources should now be passed through unmodified.

  • Handle exports named __proto__ in ES modules (#​4162, #​4163)

    In JavaScript, the special property name __proto__ sets the prototype when used inside an object literal. Previously esbuild's ESM-to-CommonJS conversion didn't special-case the property name of exports named __proto__ so the exported getter accidentally became the prototype of the object literal. It's unclear what this affects, if anything, but it's better practice to avoid this by using a computed property name in this case.

    This fix was contributed by @​magic-akari.

v0.25.3

Compare Source

  • Fix lowered async arrow functions before super() (#​4141, #​4142)

    This change makes it possible to call an async arrow function in a constructor before calling super() when targeting environments without async support, as long as the function body doesn't reference this. Here's an example (notice the change from this to null):

    // Original code
class Foo extends Object {
  constructor() {
    (async () => await foo())()
    super()
  }
}

// Old output (with --target=es2016)
class Foo extends Object {
  constructor() {
    (() => __async(this, null, function* () {
      return yield foo();
    }))();
    super();
  }
}

// New output (with --target=es2016)
class Foo extends Object {
  constructor() {
    (() => __async(null, null, function* () {
      return yield foo();
    }))();
    super();
  }
}

    Some background: Arrow functions with the async keyword are transformed into generator functions for older language targets such as --target=es2016. Since arrow functions capture this, the generated code forwards this into the body of the generator function. However, JavaScript class syntax forbids using this in a constructor before calling super(), and this forwarding was problematic since previously happened even when the function body doesn't use this. Starting with this release, esbuild will now only forward this if it's used within the function body.

    This fix was contributed by @​magic-akari.

  • Fix memory leak with --watch=true (#​4131, #​4132)

    This release fixes a memory leak with esbuild when --watch=true is used instead of --watch. Previously using --watch=true caused esbuild to continue to use more and more memory for every rebuild, but --watch=true should now behave like --watch and not leak memory.

    This bug happened because esbuild disables the garbage collector when it's not run as a long-lived process for extra speed, but esbuild's checks for which arguments cause esbuild to be a long-lived process weren't updated for the new --watch=true style of boolean command-line flags. This has been an issue since this boolean flag syntax was added in version 0.14.24 in 2022. These checks are unfortunately separate from the regular argument parser because of how esbuild's internals are organized (the command-line interface is exposed as a separate Go API so you can build your own custom esbuild CLI).

    This fix was contributed by @​mxschmitt.

  • More concise output for repeated legal comments (#​4139)

    Some libraries have many files and also use the same legal comment text in all files. Previously esbuild would copy each legal comment to the output file. Starting with this release, legal comments duplicated across separate files will now be grouped in the output file by unique comment content.

  • Allow a custom host with the development server (#​4110)

    With this release, you can now use a custom non-IP host with esbuild's local development server (either with --serve= for the CLI or with the serve() call for the API). This was previously possible, but was intentionally broken in version 0.25.0 to fix a security issue. This change adds the functionality back except that it's now opt-in and only for a single domain name that you provide.

    For example, if you add a mapping in your /etc/hosts file from local.example.com to 127.0.0.1 and then use esbuild --serve=local.example.com:8000, you will now be able to visit http://local.example.com:8000/ in your browser and successfully connect to esbuild's development server (doing that would previously have been blocked by the browser). This should also work with HTTPS if it's enabled (see esbuild's documentation for how to do that).

  • Add a limit to CSS nesting expansion (#​4114)

    With this release, esbuild will now fail with an error if there is too much CSS nesting expansion. This can happen when nested CSS is converted to CSS without nesting for older browsers as expanding CSS nesting is inherently exponential due to the resulting combinatorial explosion. The expansion limit is currently hard-coded and cannot be changed, but is extremely unlikely to trigger for real code. It exists to prevent esbuild from using too much time and/or memory. Here's an example:

    a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}

    Previously, transforming this file with --target=safari1 took 5 seconds and generated 40mb of CSS. Trying to do that will now generate the following error instead:

    ✘ [ERROR] CSS nesting is causing too much expansion

    example.css:1:60:
      1 │ a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}
        ╵                                                             ^

  CSS nesting expansion was terminated because a rule was generated with 65536 selectors. This limit
  exists to prevent esbuild from using too much time and/or memory. Please change your CSS to use
  fewer levels of nesting.

  • Fix path resolution edge case (#​4144)

    This fixes an edge case where esbuild's path resolution algorithm could deviate from node's path resolution algorithm. It involves a confusing situation where a directory shares the same file name as a file (but without the file extension). See the linked issue for specific details. This appears to be a case where esbuild is correctly following node's published resolution algorithm but where node itself is doing something different. Specifically the step LOAD_AS_FILE appears to be skipped when the input ends with ... This release changes esbuild's behavior for this edge case to match node's behavior.

  • Update Go from 1.23.7 to 1.23.8 (#​4133, #​4134)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses, such as for CVE-2025-22871.

    As a reminder, esbuild's development server is intended for development, not for production, so I do not consider most networking-related vulnerabilities in Go to be vulnerabilities in esbuild. Please do not use esbuild's development server in production.

v0.25.2

Compare Source

  • Support flags in regular expressions for the API (#​4121)

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@angular-robot angular-robot added action: review The PR is still awaiting reviews from at least one requested reviewer area: build & ci Related the build and CI infrastructure of the project labels May 12, 2025
@angular-robot angular-robot requested a review from a team May 12, 2025 08:19
@angular-robot angular-robot requested a review from a team as a code owner May 12, 2025 08:19
@angular-robot angular-robot requested review from adolgachev and ok7sai and removed request for a team May 12, 2025 08:19
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch 7 times, most recently from ce0aa52 to 81a86e0 Compare May 14, 2025 23:04
@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels May 15, 2025
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch 10 times, most recently from 5ab526b to 9c38aeb Compare May 20, 2025 23:05
@mmalerba mmalerba added the target: patch This PR is targeted for the next patch release label May 20, 2025
@angular-robot
build: update all non-major dependencies
8c3c1eb 
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch from 9c38aeb to 8c3c1eb Compare May 20, 2025 23:34
mmalerba pushed a commit to mmalerba/components that referenced this pull request May 21, 2025
@angular-robot
build: update all non-major dependencies
ca0a43a 
See associated pull request for more information.

Closes angular#31089 as a pr takeover
@mmalerba mmalerba mentioned this pull request May 21, 2025
Merged
@mmalerba mmalerba removed the action: merge The PR is ready for merge by the caretaker label May 21, 2025
mmalerba added a commit that referenced this pull request May 21, 2025
@mmalerba @angular-robot
build: update all non-major dependencies (#31164)
45ef783 
* build: update all non-major dependencies

See associated pull request for more information.

Closes #31089 as a pr takeover

* fixup! build: update all non-major dependencies

---------

Co-authored-by: Angular Robot <angular-robot@google.com>
@angular-robot angular-robot deleted the ng-renovate/all-non-major-dependencies branch May 21, 2025 15:39
@angular-automatic-lock-bot
Copy link

angular-automatic-lock-bot bot commented Jun 21, 2025

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@adolgachev adolgachev Awaiting requested review from adolgachev adolgachev was automatically assigned from angular/components-googlers

@ok7sai ok7sai Awaiting requested review from ok7sai ok7sai was automatically assigned from angular/components-googlers

Assignees

No one assigned

Labels

area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@angular-robot @mmalerba