Skip to content

The productive version of Microsoft.Testing.Extensions.HangDump must not reference to a preview version of Microsoft.Diagnostics.NETCore.Client #11981

Open

Description

Describe the bug

The package Microsoft.Testing.Extensions.HangDump in version 2.5.1 references to the package Microsoft.Diagnostics.NETCore.Client in version 0.2.607501, which is assemed to be a preview or alpha version.
A productive package like HangDump should reference to productive packages only.

Version used

Microsoft.Testing.Extensions.HangDump 2.5.1

Steps To Reproduce

N/A

Expected behavior

All references of Microsoft.Testing.Extensions.HangDump have the same release state as the package itself.

Actual behavior

Microsoft.Testing.Extensions.HangDump seems to be productive, but refers to a preview version.

Additional context

We have clear strategy to consume packages from NuGet.org. Packages are checked about the current development state. Packages should be consistent and under maintenance.
While Microsoft.Testing.Extensions.HangDump is assumed to be well maintained, the reference to Microsoft.Diagnostics.NETCore.Client 0.2.607501 breaks the chain of trust.

Activity

  1. Evangelink commented on Oct 16, 2026

    @Evangelink
    Member

    Hello!

    Thanks for the report, I'll reach out to internal team but I am not seeing any mention that this is a preview version.

  2. lg2de commented on Oct 16, 2026

    @lg2de
    Author

    If so, then please give a version 1.x.

  3. Evangelink commented on Oct 26, 2026

    @Evangelink
    Member

    Sorry for the delay, I was OOF sick last week. I am continuing the discussion with internal teams. So far, the answer seems to be that this is indeed not considered as stable but "should not be a problem".

    Do you have some strong requirement on your project/org/company or is it more of a "on principle" discussion?

  4. added
    external/otherCaused by an external issue that needs to be solved first.
    and removed
    needs/triageNeeds triage by a maintainer.
    on Oct 26, 2026
  5. lg2de commented on Oct 26, 2026

    @lg2de
    Author

    We (my company) have a package approval process. Every package, that is intended to be included in our internal (approved) package feed shall fulfill some requirements, like maintained and (quite) stable.
    For this package we need to define an exception. So, it is more than an "on principle" discussion.

    A package denoted as stable (due to version >= 1.0) should not refer to a package denoted as unstable. If it does, it cannot be really stable.

    If Microsoft.Diagnostics.NETCore.Client is working as expected, at least for Microsoft.Testing.Extensions.HangDump, is can be defined as stable, isn't it?

  6. Evangelink commented on Oct 27, 2026

    @Evangelink
    Member

    If Microsoft.Diagnostics.NETCore.Client is working as expected, at least for Microsoft.Testing.Extensions.HangDump, is can be defined as stable, isn't it?

    In theory yes :) Reality in big corps with many different teams is a little more complex but I'll push on the teams.

  7. Evangelink commented on Oct 29, 2026

    @Evangelink
    Member

    We have been able to circle back on this. The package is currently maintained but not yet shipped as v1+ because they consider the API still unstable (although there was no break in a long time). The diagnostic team will work on stabilizing the API so they can ship v1 but that might take some time.

    In the meantime, the package is correctly following semantic versioning:

    • it's not a preview package (it's maintained)
    • it's not yet v1 because API is unstable (but maintained)
    • maintenance includes security/vulnerability fixes

    If some breaks in the APIs happens, this is transparent to users of MTP because this is a deps of our HangDump extension so we would have to fix things on our side.

    The key distinction here is (un)stable vs (un)maintained: package Microsoft.Diagnostics.NETCore.Client is still unstable but it is fully supported/maintained/secured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area/dumpCrashDump / HangDump extensions.external/otherCaused by an external issue that needs to be solved first.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions