Skip to content

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented Oct 7, 2024

This PR contains the following updates:

Package Type Update Change
@types/diff (source) devDependencies patch 5.2.2 -> 5.2.3
firebase-tools devDependencies minor 13.20.2 -> 13.21.0
renovate (source) dependencies minor 38.110.2 -> 38.114.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

firebase/firebase-tools (firebase-tools)

v13.21.0

Compare Source

  • Add apphosting:rollouts:create CLI command. (#​7687)
  • Updated emulator UI to version 1.14.0, which adds support for SDK defined extensions.
  • Added emulator support for SDK defined extensions.
  • Fixed various trigger handling issues in the Functions emualtor, including an issue where Eventarc functions would not be emulated correctly after a reload.
  • Added support for generating Dart SDKs for Data Connect connectors.
  • Commands now correctly default to 'default' alias when there is more than one alias listed. (#​7624)
  • Updated Data Connect emulator to v1.15.0, which includes bug fixes for insertMany and improved error handling.
renovatebot/renovate (renovate)

v38.114.0

Compare Source

Features

v38.113.0

Compare Source

Features

v38.112.0

Compare Source

Features
  • manager/azure-pipelines: Include .azuredevops folder paths (#​31735) (076fc9a)

v38.111.1

Compare Source

Bug Fixes
Code Refactoring

v38.111.0

Compare Source

Features
Miscellaneous Chores

v38.110.5

Compare Source

Bug Fixes
  • deps: update ghcr.io/renovatebot/base-image docker tag to v7.34.2 (#​31848) (1ce3d7c)
Miscellaneous Chores
  • deps: update containerbase/internal-tools action to v3.4.27 (#​31847) (296f248)

v38.110.4

Compare Source

Bug Fixes
  • deps: update ghcr.io/containerbase/sidecar docker tag to v11.11.30 (#​31845) (b5128d5)
Miscellaneous Chores

v38.110.3

Compare Source

Bug Fixes
Documentation
Miscellaneous Chores
Code Refactoring

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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: merge The PR is ready for merge by the caretaker comp: build renovate managed labels Oct 7, 2024
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Oct 7, 2024
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch 5 times, most recently from 4bf9412 to a46376f Compare October 8, 2024 10:10
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch from a46376f to 82e15ef Compare October 8, 2024 12:15
@angular-robot
Copy link
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package.json
Command failed: yarn update-generated-files
2024/10/08 12:08:07 Downloading https://releases.bazel.build/5.4.0/release/bazel-5.4.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
INFO: Repository nodejs_linux_amd64 instantiated at:
  /tmp/renovate/repos/github/angular/dev-infra/WORKSPACE:41:27: in <toplevel>
  /home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/external/rules_nodejs/nodejs/repositories.bzl:404:26: in nodejs_register_toolchains
Repository rule node_repositories defined at:
  /home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/external/rules_nodejs/nodejs/repositories.bzl:378:36: in <toplevel>
WARNING: Download from https://nodejs.org/dist/v18.20.0/node-v18.20.0-linux-x64.tar.xz failed: class java.io.IOException Read timed out
ERROR: An error occurred during the fetch of repository 'nodejs_linux_amd64':
   Traceback (most recent call last):
	File "/home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/external/rules_nodejs/nodejs/repositories.bzl", line 375, column 19, in _nodejs_repo_impl
		_download_node(repository_ctx)
	File "/home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/external/rules_nodejs/nodejs/repositories.bzl", line 184, column 40, in _download_node
		repository_ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://nodejs.org/dist/v18.20.0/node-v18.20.0-linux-x64.tar.xz] to /home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/external/nodejs_linux_amd64/bin/nodejs/temp9047139074765056362/node-v18.20.0-linux-x64.tar.xz: Read timed out
ERROR: /tmp/renovate/repos/github/angular/dev-infra/WORKSPACE:41:27: fetching node_repositories rule //external:nodejs_linux_amd64: Traceback (most recent call last):
	File "/home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/external/rules_nodejs/nodejs/repositories.bzl", line 375, column 19, in _nodejs_repo_impl
		_download_node(repository_ctx)
	File "/home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/external/rules_nodejs/nodejs/repositories.bzl", line 184, column 40, in _download_node
		repository_ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://nodejs.org/dist/v18.20.0/node-v18.20.0-linux-x64.tar.xz] to /home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/external/nodejs_linux_amd64/bin/nodejs/temp9047139074765056362/node-v18.20.0-linux-x64.tar.xz: Read timed out
ERROR: error loading package '': Encountered error while reading extension file '@bazel/protractor/package.bzl': no such package '@npm//@bazel/protractor': no such package '@nodejs_linux_amd64//': java.io.IOException: Error downloading [https://nodejs.org/dist/v18.20.0/node-v18.20.0-linux-x64.tar.xz] to /home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/external/nodejs_linux_amd64/bin/nodejs/temp9047139074765056362/node-v18.20.0-linux-x64.tar.xz: Read timed out
INFO: Elapsed time: 225.374s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
FAILED: Build did NOT complete successfully (0 packages loaded)

Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@josephperrott
Copy link
Member

This PR was merged into the repository by commit a566262.

The changes were merged into the following branches: main

@angular-robot angular-robot deleted the ng-renovate/all-non-major-dependencies branch October 8, 2024 15:09
@angular-automatic-lock-bot
Copy link

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 Nov 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project comp: build renovate managed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants