fix supported versions

[Stephan van Rooij (svrooij)]

It is a mistery to my why the cli is only supporting very old versions. Here is a version bump for node an dotnet-isolated which for some reason are referenced as dotnetisolated only in this repository.

And you might want to change the config specification to also reflect this..... schemastore.org/staticwebapp.config.json

{
    "platform": {
      "type": "object",
      "description": "Platform configuration",
      "properties": {
        "apiRuntime": {
          "type": "string",
          "enum": [
            "dotnet:3.1",
            "dotnet:6.0",
            "dotnet-isolated:6.0",
            "dotnet-isolated:7.0",
            "dotnet-isolated:8.0",
            "dotnet-isolated:9.0",
            "node:12",
            "node:14",
            "node:16",
            "node:18",
            "node:20",
            "python:3.8",
            "python:3.9",
            "python:3.10"
          ],
          "description": "Language runtime for the managed functions API"
        }
      },
      "additionalProperties": false
    },
}

[Simone Chiaretta (simonechGSC)]

I had just created a ticket before seeing this PR :)
#1002

[Stephan van Rooij (svrooij)]

Simone Chiaretta (@simonechGSC) just deploy your app with dotnetisolated and 8.0 as parameters. I successfully deployed my dotnet-isolated v10 app using those parameters. Then you can continue with your day while they might accept this pr

[Simone Chiaretta (simonechGSC)]

Simone Chiaretta (@simonechGSC) just deploy your app with dotnetisolated and 8.0 as parameters. I successfully deployed my dotnet-isolated v10 app using those parameters. Then you can continue with your day while they might accept this pr

That's indeed what I did... I wonder what is the purpose of that parameter if is not taken into account

[Stephan van Rooij (svrooij)]

Great question for the team that developed this cli.
I'm wondering the same, and I'm glad I found a way that works.

[Jikun (cjk7989)]

Hi Stephan van Rooij (@svrooij), thank you very much for the contribution. StaticWebApps platform haven't supported node 24, 26 currently, so just making changes on SWA-CLI will not help. We will support them in the future. See https://learn.microsoft.com/en-us/azure/static-web-apps/languages-runtimes

[Simone Chiaretta (simonechGSC)]

Hi Stephan van Rooij (@svrooij), thank you very much for the contribution. StaticWebApps platform haven't supported node 24, 26 currently, so just making changes on SWA-CLI will not help. We will support them in the future. See https://learn.microsoft.com/en-us/azure/static-web-apps/languages-runtimes

According to that page, net10 is not supported either, but I deploy it, it works fine.
.NET 10 is the currently supported LTS, seems strange SWA are not supporting it yet... is this SWA a "dying" service or is it there to stay?

Also that page was last updated in february 2025, not really up to date

[Stephan van Rooij (svrooij)]

Jikun (@cjk7989) I removed the node versions (that should be supported), and made it accept both dotnet-isolated (as any other cli from microsoft) and dotnetisolated to keep others from mistakes.

[Stephan van Rooij (svrooij)]

Jikun (@cjk7989) care to have a look at this PR? It is an easy fix that will unblock others. While not changing anything mayor.

Not officially supporting dotnet 10 really makes users of Swa nervous, and they start asking questions if SWA is still a product Microsoft wants to support.