Initial Triage for New Issue

[Bug]: Don't Use Memory Attribute Protocol in Core and Optimize SetMemoryAttributes #89

Sign in to view logs

Triggered via issue September 3, 2024 22:03

os-d

opened #1132 2acf969

Status Success

Total duration 19s

Artifacts –

triage-issues.yml

on: issues

Matrix: triage / Triage Issues

Annotations

3 warnings

triage / Triage Issues (feature_request.yml)

The following actions use a deprecated Node.js version and will be forced to run on node20: redhat-plumbers-in-action/advanced-issue-labeler@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

triage / Triage Issues (documentation_request.yml)

The following actions use a deprecated Node.js version and will be forced to run on node20: redhat-plumbers-in-action/advanced-issue-labeler@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

triage / Triage Issues (bug_report.yml)

The following actions use a deprecated Node.js version and will be forced to run on node20: redhat-plumbers-in-action/advanced-issue-labeler@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/