Merged
Conversation
Contributor
Author
|
renovate
bot
force-pushed
the
renovate/all
branch
7 times, most recently
from
8084f90 to
d6f906f
Compare
adrianriobo
force-pushed
the
renovate/all
branch
from
d6f906f to
f795fb1
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR contains the following updates:
2.317.0->2.327.1v0.135.0->v0.147.0v1.36.6->v1.37.1v1.6.11->v1.7.0v1.29.18->v1.30.2v1.17.71->v1.18.2v1.16.33->v1.18.1v1.3.37->v1.4.1v2.6.37->v2.7.1v1.3.37->v1.4.1v1.233.1->v1.239.0v1.60.1->v1.61.1v1.43.1->v1.44.1v1.12.4->v1.13.0v1.7.5->v1.8.1v1.12.18->v1.13.1v1.18.18->v1.19.1v1.35.1->v1.36.1v1.84.1->v1.85.1v1.25.6->v1.26.1v1.30.4->v1.31.1v1.34.1->v1.35.1v5.2.3->v5.3.0v2.2.2->v2.3.0v0.9.0->v0.10.0v0.19.1->v0.20.0v1.22.0->v1.23.0v0.14.3->v0.16.0v3.185.0->v3.187.0v0.9.0->v0.10.0v0.3.5->v0.4.07130f93->f173205v1.73.0->v1.74.23.184.0->3.187.0v7.0.0->v7.2.0v2.22.0->v3.0.06fd64cd->3ce631161bf5be->0fa3e48Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/runner (actions/runner)
v2.327.1Compare Source
What's Changed
New Contributors
Full Changelog: actions/runner@v2.326.0...v2.327.0
Note: Actions Runner follows a progressive release policy, so the latest release might not be available to your enterprise, organization, or repository yet.
To confirm which version of the Actions Runner you should expect, please view the download instructions for your enterprise, organization, or repository.
See https://docs.github.com/en/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners
Windows x64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:Windows arm64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:OSX x64
OSX arm64 (Apple silicon)
Linux x64
Linux arm64
Linux arm
Using your self hosted runner
For additional details about configuring, running, or shutting down the runner please check out our product docs.
SHA-256 Checksums
The SHA-256 checksums for the packages included in this build are shown below:
v2.327.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/runner@v2.326.0...v2.327.0
Note: Actions Runner follows a progressive release policy, so the latest release might not be available to your enterprise, organization, or repository yet.
To confirm which version of the Actions Runner you should expect, please view the download instructions for your enterprise, organization, or repository.
See https://docs.github.com/en/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners
Windows x64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:Windows arm64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:OSX x64
OSX arm64 (Apple silicon)
Linux x64
Linux arm64
Linux arm
Using your self hosted runner
For additional details about configuring, running, or shutting down the runner please check out our product docs.
SHA-256 Checksums
The SHA-256 checksums for the packages included in this build are shown below:
v2.326.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/runner@v2.325.0...v2.326.0
Note: Actions Runner follows a progressive release policy, so the latest release might not be available to your enterprise, organization, or repository yet.
To confirm which version of the Actions Runner you should expect, please view the download instructions for your enterprise, organization, or repository.
See https://docs.github.com/en/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners
Windows x64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:Windows arm64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:OSX x64
OSX arm64 (Apple silicon)
Linux x64
Linux arm64
Linux arm
Using your self hosted runner
For additional details about configuring, running, or shutting down the runner please check out our product docs.
SHA-256 Checksums
The SHA-256 checksums for the packages included in this build are shown below:
v2.325.0Compare Source
What's Changed
Full Changelog: actions/runner@v2.324.0...v2.325.0
Note: Actions Runner follows a progressive release policy, so the latest release might not be available to your enterprise, organization, or repository yet.
To confirm which version of the Actions Runner you should expect, please view the download instructions for your enterprise, organization, or repository.
See https://docs.github.com/en/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners
Windows x64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:Windows arm64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:OSX x64
OSX arm64 (Apple silicon)
Linux x64
Linux arm64
Linux arm
Using your self hosted runner
For additional details about configuring, running, or shutting down the runner please check out our product docs.
SHA-256 Checksums
The SHA-256 checksums for the packages included in this build are shown below:
v2.324.0Compare Source
What's Changed
JobContext.CheckRunIDby @pje in https://github.com/actions/runner/pull/3811New Contributors
Full Changelog: actions/runner@v2.323.0...v2.324.0
Note: Actions Runner follows a progressive release policy, so the latest release might not be available to your enterprise, organization, or repository yet.
To confirm which version of the Actions Runner you should expect, please view the download instructions for your enterprise, organization, or repository.
See https://docs.github.com/en/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners
Windows x64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:Windows arm64
We recommend configuring the runner in a root folder of the Windows drive (e.g. "C:\actions-runner"). This will help avoid issues related to service identity folder permissions and long file path restrictions on Windows.
The following snipped needs to be run on
powershell:OSX x64
OSX arm64 (Apple silicon)
Linux x64
Linux arm64
Linux arm
Using your self hosted runner
For additional details about configuring, running, or shutting down the runner please check out our product docs.
SHA-256 Checksums
The SHA-256 checksums for the packages included in this build are shown below:
v2.323.0Compare Source
What's Changed
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.