Skip to content

feat(rendering): pipeline V2 con tone parity, LOD e fallback DWrite safe #1

feat(rendering): pipeline V2 con tone parity, LOD e fallback DWrite safe

feat(rendering): pipeline V2 con tone parity, LOD e fallback DWrite safe #1

Triggered via push April 6, 2026 00:13
Status Failure
Total duration 2m 6s
Artifacts

release.yml

on: push
build-and-release
2m 3s
build-and-release
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
build-and-release: PuretypeUI/MainWindow.xaml.cs#L576
The name 'QdSepGen1ValText' does not exist in the current context
build-and-release: PuretypeUI/MainWindow.xaml.cs#L477
The name 'ChromaKeepWoledSlider' does not exist in the current context
build-and-release: PuretypeUI/MainWindow.xaml.cs#L476
The name 'ChromaKeepQdSlider' does not exist in the current context
build-and-release: PuretypeUI/MainWindow.xaml.cs#L475
The name 'QdVerticalBlendSlider' does not exist in the current context
build-and-release: PuretypeUI/MainWindow.xaml.cs#L474
The name 'QdSepGen4Slider' does not exist in the current context
build-and-release: PuretypeUI/MainWindow.xaml.cs#L473
The name 'QdSepGen3Slider' does not exist in the current context
build-and-release: PuretypeUI/MainWindow.xaml.cs#L472
The name 'QdSepGen1Slider' does not exist in the current context
build-and-release: PuretypeUI/MainWindow.xaml.cs#L232
The name 'PageAdvanced' does not exist in the current context
build-and-release: PuretypeUI/MainWindow.xaml.cs#L232
The name 'TabAdvanced' does not exist in the current context
build-and-release: PuretypeUI/MainWindow.xaml.cs#L182
The name 'PageAdvanced' does not exist in the current context
build-and-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, ilammy/msvc-dev-cmd@v1. 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/