Skip to content

Clarify VMware import conversion storage option #18093

Clarify VMware import conversion storage option

Clarify VMware import conversion storage option #18093

Triggered via pull request May 15, 2026 01:07
Status Success
Total duration 12s
Artifacts

merge-conflict-checker.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
triage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: eps1lon/actions-label-merge-conflict@v3.0.3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
triage
could not remove label "status:has-conflicts": Worflows can't access secrets and have read-only access to upstream when they are triggered by a pull request from a fork, [more information](https://docs.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token)
triage
could not remove label "status:has-conflicts": Worflows can't access secrets and have read-only access to upstream when they are triggered by a pull request from a fork, [more information](https://docs.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#permissions-for-the-github_token)