releases #348
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
releases.yml
on: schedule
list-manifest-versions
3s
Matrix: check
Annotations
19 errors and 17 warnings
check (1.3.13)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (2.8.0)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (2.7.1)
The job was canceled because "_1_3_13" failed.
|
check (2.7.1)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (1.3.8)
The job was canceled because "_1_3_13" failed.
|
check (1.3.8)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (1.4.0)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (2.6.1)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (2.9.1)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (1.3.10)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (1.3.9)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (1.3.12)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (2.7.0)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (2.8.1)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (2.10.0)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (2.9.0)
The operation was canceled.
|
check (2.6.0)
An error occurred while creating the issue. This might be caused by a malformed issue title, or a typo in the labels or assignees. Check .github/ISSUE_TEMPLATE/release_template.md!
Issues are disabled for this repo
|
check (3.0.0)
The operation was canceled.
|
check (1.3.11)
The operation was canceled.
|
list-manifest-versions
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
check (1.3.13)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (2.8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (2.7.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (1.4.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (2.6.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (2.9.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (1.3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (1.3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (1.3.12)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (2.7.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (2.8.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (2.10.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (2.9.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (2.6.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (3.0.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
check (1.3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: dblock/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|