Skip to content

Clarify that global.json version field doesn't support 9.0.x, 9.0.0 or 9.0 values #47455

Closed

Description

@Frulfump

Type of issue

Typo

Description

As evident by
dependabot/dependabot-core#12396
microsoft/azure-pipelines-tasks#19292 (comment)

People don't seem to understand what constitutes a valid version string. So let's help people by calling out some specific invalid values.

Related dotnet/sdk#49816
Related PR adding reporting for invalid versions when doing dotnet --info dotnet/runtime#118418 also includes 9.0 as an invalid value together with 9.0.x and 9.0.0.

(Type of issue should probably be "Missing information" but I don't want to break any automation)

Page URL

https://learn.microsoft.com/en-us/dotnet/core/tools/global-json#version

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/tools/global-json.md

Document Version Independent Id

6d80613f-42dc-35d7-aeff-3187a36dbbca

Platform Id

8e1f5348-e2c6-2d5e-9531-202d840f33ca

Article author

@tdykstra

Metadata

  • ID: a94c335b-0b65-96cc-1c25-65777fbe4bb5
  • PlatformId: 8e1f5348-e2c6-2d5e-9531-202d840f33ca
  • Service: dotnet-fundamentals

Related Issues


Associated WorkItem - 503525

Activity

  1. Frulfump commented on Aug 17, 2025

    @Frulfump
    Author

    9.0 will also show an error when doing dotnet --info as well as 9.0.0 and 9.0.x
    after dotnet/runtime#118418 is released

  2. changed the title [-]Clarify that `global.json` `version` field doesn't support `9.0.x` or `9.0.0` values[/-] [+]Clarify that `global.json` `version` field doesn't support `9.0.x`, `9.0.0` or `9.0` values[/+] on Aug 17, 2025
  3. self-assigned this
    on Oct 21, 2025
  4. added
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Oct 28, 2025
  5. removed
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Oct 28, 2025
  6. added
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Oct 28, 2025
  7. removed
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Oct 28, 2025
  8. added
    📌 seQUESTeredIdentifies that an issue has been imported into Quest.
    and removed
    🗺️ reQUESTTriggers an issue to be imported into Quest.
    on Oct 30, 2025
  9. moved this from 🔖 Ready to 🏗 In progress in dotnet/docs November 2025 sprinton Nov 17, 2025
  10. moved this from 🏗 In progress to ✅ Done in dotnet/docs November 2025 sprinton Nov 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions