-
Notifications
You must be signed in to change notification settings - Fork 49
build: lock file maintenance #136
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.
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
Open
angular-robot
wants to merge
1
commit into
angular:main
from
angular-robot:ng-renovate/lock-file-maintenance
Open
build: lock file maintenance #136
angular-robot
wants to merge
1
commit into
angular:main
from
angular-robot:ng-renovate/lock-file-maintenance
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
angular-robot
commented
Oct 28, 2025
⚠️ 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: runner/testing/browser-agent/uv.lock
Command failed: uv lock --upgrade
/bin/sh: 1: uv: not found
@angular-robot
angular-robot
force-pushed
the
ng-renovate/lock-file-maintenance
branch
from
October 28, 2025 04:05
1a1f968 to
ee35461
Compare
@angular-robot
angular-robot
requested review from
AndrewKushnir,
crisbeto and
devversion
as code owners
October 28, 2025 04:05
@angular-robot
angular-robot
force-pushed
the
ng-renovate/lock-file-maintenance
branch
3 times, most recently
from
November 3, 2025 19:04
7f2a4c8 to
8e7acbe
Compare
@angular-robot
angular-robot
force-pushed
the
ng-renovate/lock-file-maintenance
branch
2 times, most recently
from
November 13, 2025 08:05
b4d384a to
207a347
Compare
@angular-robot
angular-robot
force-pushed
the
ng-renovate/lock-file-maintenance
branch
2 times, most recently
from
November 19, 2025 08:06
dee0014 to
81cd7b1
Compare
See associated pull request for more information.
@angular-robot
angular-robot
force-pushed
the
ng-renovate/lock-file-maintenance
branch
from
November 20, 2025 18:07
81cd7b1 to
cf34d5c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.