feat: wdk_build::DerivesMap for derives collection of bindgen output
#4319
leon-xdAnnotations
36 warnings and 12 notices
|
Test (windows-11-arm, arm64, 10.0.26100, nuget, 17.0.6, beta, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.26100, nuget, 17.0.6, nightly, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.26100, nuget, 17.0.6, stable, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, beta, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, beta, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.26100, nuget, 17.0.6, nightly, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.26100, nuget, 17.0.6, stable, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, stable, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, stable, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.26100, nuget, 17.0.6, beta, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, nightly, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, nightly, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, nightly, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, nightly, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, beta, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, beta, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.22621, winget, 17.0.6, nightly, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.22621, winget, 17.0.6, nightly, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, beta, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, beta, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, nightly, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, nightly, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, stable, dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, stable, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.22621, winget, 17.0.6, stable, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.22621, winget, 17.0.6, beta, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, beta, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, beta, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, stable, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, stable, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.22621, winget, 17.0.6, stable, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-11-arm, arm64, 10.0.22621, winget, 17.0.6, beta, dev)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (aarch64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, nightly, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, nightly, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, stable, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, stable, release)
install-action: cargo-binstall fallback does not support prebuilt binaries for cargo-expand@1.0.85 on this platform (x86_64); use 'cargo-install' fallback instead
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, beta, dev)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, stable, dev)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, nightly, dev)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, nightly, release)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, beta, release)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, beta, dev)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, nightly, dev)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, stable, dev)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, beta, release)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.26100, nuget, 17.0.6, stable, release)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, nightly, release)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test (windows-2025, amd64, 10.0.22621, winget, 17.0.6, stable, release)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|