Docker Image used by SWA Github Actions not picking latest Oryx, causing builds to fail for latest global.json SDK

[Benny-TalentzQ]

Describe the bug

Our repository contains the following global.json:

{
  "sdk": {
    "version": "8.0.422",
    "rollForward": "latestPatch"
  }
}

During deployment, Oryx detected the application and dynamically installed .NET SDK 8.0.420 instead of the SDK requested by global.json (8.0.422).

The subsequent build failed because the .NET SDK resolver correctly requires 8.0.422 (or a later patch in the same feature band) and cannot roll back to 8.0.420.

---Oryx build logs---

Oryx Version: 0.2.20260109.4+7d54dd5970dbbf3ae6bdcf4dee57b07816a392ce, Commit: 7d54dd5970dbbf3ae6bdcf4dee57b07816a392ce, ReleaseTagName: 20260109.4

The docker image used by the SWA GitHub actions is not picking up the latest Orxy version

A clarification has also been sought from microsoft/Oryx#3017 to understand if the issue is to be addressed at SWA GitHub actions or the Oryx release cycle.

To Reproduce
Steps to reproduce the behavior:

1. Create a .NET 8 application.
2. Add the following global.json:

{
  "sdk": {
    "version": "8.0.422",
    "rollForward": "latestPatch"
  }
}

3. Deploy the application to Azure Static Web Apps using the Azure/static-web-apps-deploy GitHub Action.
4. Perform the deployment before Oryx has been updated to include the requested SDK version.
5. Observe that Oryx installs .NET SDK 8.0.420, after which the build fails because global.json requires 8.0.422.

Expected behavior
Ideally one of the following:

1. New GA .NET SDKs once become available in Oryx should also be picked up by the docker image used by the SWA GitHub actions so that repositories can adopt the latest SDK without deployment failures.

The current behavior forces developers to either delay SDK updates, pin to an older SDK, or wait until the updated Oryx image is deployed.

Screenshots
If applicable, add screenshots to help explain your problem.

Device info (if applicable):

• OS: Ubuntu 24.04.4 LTS
• Version: static-web-apps-deploy@1a947af9992250f3bc2e68ad0754c0b0c11566c9
• OS Type : bullseye
• Image Type : githubactions

Additional context

• SDK update appears to already exist in Oryx PR #2933, but it is not yet available in the Oryx version used by Azure Static Web Apps.

Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
You can report issues at https://github.com/Microsoft/Oryx/issues

Oryx Version: 0.2.20260109.4+7d54dd5970dbbf3ae6bdcf4dee57b07816a392ce, Commit: 7d54dd5970dbbf3ae6bdcf4dee57b07816a392ce, ReleaseTagName: 20260109.4

Build Operation ID: 656d1080a8dcbcf6
OS Type           : bullseye
Image Type        : githubactions

Primary SDK Storage URL: https://oryx-cdn.microsoft.io/
Backup SDK Storage URL: 
Detecting platforms...
Detected following platforms:
  dotnet: 8.0.26
Version '8.0.26' of platform 'dotnet' is not installed. Generating script to install it...
Detected the following frameworks: blazor


Source directory     : /github/workspace/CareerWeb
Destination directory: /bin/staticsites/47f7c9f1-9f92-42a0-866d-7917613ceddb-swa-oryx/app

Installing platform...

Downloading and extracting 'dotnet' version '8.0.420' to '/tmp/oryx/platforms/dotnet/8.0.420'...
Detected image debian flavor: bullseye.
Binaries download done in 3 sec(s).
Verifying checksum...
Extracting contents...
performing sha512 checksum for: dotnet...
Checksum verification done in 1 sec(s).

Platform installation done in 8 sec(s).
Running build script snippets...

The command could not be loaded, possibly because:
  * You intended to execute a .NET application:
      The application '--version' does not exist.
  * You intended to execute a .NET SDK command:
      A compatible .NET SDK was not found.

Requested SDK version: 8.0.422
global.json file: /github/workspace/global.json

Installed SDKs:

Install the [8.0.422] .NET SDK or update [/github/workspace/global.json] to match an installed SDK.

Thank you for taking a look. I understand there may be operational reasons for the delay, but greater visibility into the release cadence—or more informative diagnostics when the requested SDK is unavailable—would significantly improve the developer experience.