version-aspnetcoremodule is empty in releases.json starting from 10.0 preview 4

[jberezanski]

In the releases.json file for 10.0, the value of version-aspnetcoremodule is blank in preview 4 and preview 5:

  "releases": [
    {
      "release-date": "2025-06-10",
      "release-version": "10.0.0-preview.5",
      "security": false,
      "cve-list": [],
      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/10.0/preview/preview5/10.0.0-preview.5.md",
      "runtime": { ...  },
      "sdk": { ...  },
      "sdks": [ ... ],
      "aspnetcore-runtime": {
        "version": "10.0.0-preview.5.25277.114",
        "version-display": "10.0.0-preview.5",
        "version-aspnetcoremodule": [],                <-- empty

In preview 3 and earlier, this field was filled:

    {
      "release-date": "2025-04-10",
      "release-version": "10.0.0-preview.3",
      "security": false,
      "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/10.0/preview/preview3/10.0.0-preview.3.md",
      "runtime": { ...  },
      "sdk": { ...  },
      "sdks": [ ... ],
      "aspnetcore-runtime": {
        "version": "10.0.0-preview.3.25172.1",
        "version-display": "10.0.0-preview.3",
        "version-aspnetcoremodule": [
          "20.0.25082.0"
        ],

Is this an accidental omission or is this field being deprecated and will not be filled in future?

[wfurt]

any thoughts on this @jozkee ?

[leecow]

@pavel-purma - possibly related to your pipeline work?

[pavel-purma]

This is related to new pipeline code. The problem was that I have no story how to figure out the version from assets produced by Unified Build. We had a quick chat about that with @mmitche . If I remember well outcome was, we maybe don't need this info anymore.

[jberezanski]

I'm the maintainer of .NET Core packages on the Chocolatey Community Repository. One of the packages is designed to install just the ASP.NET Core Module (without any runtimes), to facilitate some hosting scenarios. The versioning of that package follows the version of the ANCM and I use the version-aspnetcoremodule field in an automated process, which updates the package after each .NET release. Right now, for .NET 10, the automation does not work and I need to add the correct version number by hand, which is not an acceptable long term solution for me. If the field is no longer set, I will have to develop another way to obtain this information, possibly by decompiling the installer exe, and I would very much prefer to avoid doing that.

So, I would appreciate it very much if you would find some way to restore this information in the new pipeline.

[mmitche]

@pavel-purma How did we figure this out in the old pipeline?

[jberezanski]

Is there a chance this will be fixed before .NET 10 RTM?

[jberezanski]

I can see the field is now populated in RC 2:

      "aspnetcore-runtime": {
        "version": "10.0.0-rc.2.25502.107",
        "version-display": "10.0.0-rc.2",
        "version-aspnetcoremodule": ["20.0.25275.0"],

Thank you!