-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.319.1) #24
Merged
Conversation
This file contains 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
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
February 27, 2024 23:18
2933357
to
6aa19ed
Compare
monova-bot
bot
changed the title
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.314.0)
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.314.1)
Feb 27, 2024
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
March 19, 2024 14:19
6aa19ed
to
4e319cb
Compare
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
March 26, 2024 20:20
4e319cb
to
46063b1
Compare
monova-bot
bot
changed the title
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.314.1)
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.315.0)
Mar 26, 2024
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
March 27, 2024 09:20
46063b1
to
8cac1c4
Compare
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
2 times, most recently
from
April 14, 2024 22:12
855803a
to
1486dfe
Compare
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
April 23, 2024 16:25
1486dfe
to
502c07b
Compare
monova-bot
bot
changed the title
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.315.0)
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.316.0)
Apr 23, 2024
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
May 2, 2024 18:26
502c07b
to
8927053
Compare
monova-bot
bot
changed the title
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.316.0)
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.316.1)
May 2, 2024
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
May 30, 2024 17:19
8927053
to
e9649ba
Compare
monova-bot
bot
changed the title
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.316.1)
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.317.0)
May 30, 2024
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
July 26, 2024 16:28
e9649ba
to
2e3e562
Compare
monova-bot
bot
changed the title
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.317.0)
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.318.0)
Jul 26, 2024
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
August 8, 2024 15:25
2e3e562
to
321ac16
Compare
monova-bot
bot
changed the title
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.318.0)
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.319.0)
Aug 8, 2024
…19.1) Signed-off-by: monova-bot[bot] <160980066+monova-bot[bot]@users.noreply.github.com>
monova-bot
bot
force-pushed
the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
from
August 13, 2024 17:21
321ac16
to
3dab605
Compare
monova-bot
bot
changed the title
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.319.0)
feat(container): update ghcr.io/onedr0p/actions-runner (2.313.0 → 2.319.1)
Aug 13, 2024
monova-bot
bot
deleted the
renovate/ghcr.io-onedr0p-actions-runner-2.x
branch
September 7, 2024 12:38
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.
This PR contains the following updates:
2.313.0
->2.319.1
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/runner (ghcr.io/onedr0p/actions-runner)
v2.319.1
Compare Source
What's Changed
Full Changelog: actions/runner@v2.319.0...v2.319.1
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
:[Pre-release] Windows arm64
Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.
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.319.0
Compare Source
What's Changed
Full Changelog: actions/runner@v2.318.0...v2.319.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
:[Pre-release] Windows arm64
Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.
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.318.0
Compare Source
What's Changed
Full Changelog: actions/runner@v2.317.0...v2.318.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
:[Pre-release] Windows arm64
Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.
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.317.0
Compare Source
What's Changed
git
on an Action Runner Image by @jww3 in https://github.com/actions/runner/pull/3273gpg-agent
during actions/runner container image build by @jww3 in https://github.com/actions/runner/pull/3294Full Changelog: actions/runner@v2.316.1...v2.317.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
:[Pre-release] Windows arm64
Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.
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.316.1
Compare Source
What's Changed
Full Changelog: actions/runner@v2.316.0...v2.316.1
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
:[Pre-release] Windows arm64
Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.
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.316.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/runner@v2.315.0...v2.316.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
:[Pre-release] Windows arm64
Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.
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.315.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/runner@v2.314.1...v2.315.0
Full Changelog: actions/runner@v2.313.0...v2.314.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
:[Pre-release] Windows arm64
Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.
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.314.1
Compare Source
What's Changed
snapshot
tokens by @davidomid in https://github.com/actions/runner/pull/3135New Contributors
Full Changelog: actions/runner@v2.313.0...v2.314.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
:[Pre-release] Windows arm64
Warning: Windows arm64 runners are currently in preview status and use unofficial versions of nodejs. They are not intended for production workflows.
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.314.0
Compare Source
What's Changed
snapshot
tokens by @davidomid in https://github.com/actions/runner/pull/3135Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.