Skip to content

Conversation

angular-robot
Copy link
Collaborator

@angular-robot angular-robot commented Dec 16, 2024

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 4am on monday" 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: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release labels Dec 16, 2024
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Dec 16, 2024
@angular-robot
Copy link
Collaborator Author

angular-robot commented Dec 16, 2024

⚠️ 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: pnpm-lock.yaml
/bin/sh: 1: pnpm: not found

@dgp1130
Copy link
Collaborator

dgp1130 commented Dec 17, 2024

I feel like the pnpm error is probably related to @aspect_rules_js, not this PR. But I'll hold off on merging it until our infra is in a stable state to get a passing validation, as this doesn't seem terribly urgent.

@angular-robot angular-robot force-pushed the ng-renovate/lock-file-maintenance branch 4 times, most recently from 9e738b7 to 85928c5 Compare December 17, 2024 17:22
@alan-agius4 alan-agius4 removed the action: merge The PR is ready for merge by the caretaker label Dec 17, 2024
@angular-robot angular-robot force-pushed the ng-renovate/lock-file-maintenance branch from 85928c5 to 3ad6b4a Compare December 17, 2024 18:00
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Dec 17, 2024
@clydin clydin merged commit 60c79c0 into angular:main Dec 17, 2024
31 checks passed
@alan-agius4 alan-agius4 deleted the ng-renovate/lock-file-maintenance branch December 17, 2024 18:39
@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 Jan 17, 2025
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 target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants