Skip to content

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented Dec 9, 2025

This PR contains the following updates:

Package Type Update Change
@angular/ng-dev devDependencies digest 19b0de8 -> 9eb95b3
angular/dev-infra action digest fabf48e -> 4ec8405
devinfra git_override digest fabf48e -> 4ec8405

🔡 If you wish to disable git hash updates, add ":disableDigestUpdates" to the extends array in your config.


Configuration

📅 Schedule: Branch creation - Every 2 hours, between 12:00 AM and 10:59 PM ( * 0-22/2 * * * ) in timezone Europe/Rome, 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 area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only] labels Dec 9, 2025
@ngbot
Copy link

ngbot bot commented Dec 9, 2025

I see that you just added the action: merge label, but the following checks are still failing:
    failure conflicts with base branch "21.0.x"
    failure status "mergeability" is failing
If you want your PR to be merged, it has to pass all the CI checks.
If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

1 similar comment
@ngbot
Copy link

ngbot bot commented Dec 9, 2025

I see that you just added the action: merge label, but the following checks are still failing:
    failure conflicts with base branch "21.0.x"
    failure status "mergeability" is failing
If you want your PR to be merged, it has to pass all the CI checks.
If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@angular-robot angular-robot changed the title build: update cross-repo angular dependencies to 4ec8405 (21.0.x) build: update cross-repo angular dependencies (21.0.x) Dec 9, 2025
@angular-robot angular-robot force-pushed the ng-renovate/21.0.x-cross-repo-angular-dependencies branch from ca5211b to ad65e6e Compare December 9, 2025 16:07
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/21.0.x-cross-repo-angular-dependencies branch from ad65e6e to 32cd1c1 Compare December 9, 2025 21:05
@hybrist hybrist merged commit 7b063de into angular:21.0.x Dec 10, 2025
34 checks passed
@hybrist
Copy link
Contributor

hybrist commented Dec 10, 2025

This PR was merged into the repository. The changes were merged into the following branches:

@angular-robot angular-robot deleted the ng-renovate/21.0.x-cross-repo-angular-dependencies branch December 10, 2025 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants