Skip to content

Conversation

@hybrist
Copy link
Contributor

@hybrist hybrist commented Nov 12, 2025

It looks like this lockfile got broken (somehow) in #31761 or while landing the PR. I'm not sure how that was possible since CI is passing for the PR but not after landing on main..?

@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Nov 12, 2025
@hybrist
Copy link
Contributor Author

hybrist commented Nov 12, 2025

(Main is currently red without the regenerated lock file.)

@hybrist hybrist added target: automation This PR is targeted to only merge into the branch defined in Github [bot use only] action: review The PR is still awaiting reviews from at least one requested reviewer labels Nov 12, 2025
@hybrist hybrist 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 Nov 12, 2025
@hybrist hybrist merged commit 067004d into angular:main Nov 12, 2025
34 of 35 checks passed
@hybrist hybrist deleted the jk-lock-file-healing branch November 12, 2025 18:04
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