Octokit v9.0 introduced 'Artifact' into global namespace

[amis92]

Usage Information

NUKE v8.0

Description

Octokit dependency update to v9 in NUKE v8 has introduced an Artifact type into global namespace, which collides with any self-declared type like that and requires workarounds like extern alias.

There's been a bugfix and Octokit v9.1.1 with it is available. See octokit/octokit.net#2861

Reproduction Steps

namespace N1 {
    public class Artifact { }
}
namespace N2 {
    using Artifact = N1.Artifact; // error
    public class C : Artifact { }
}

Expected Behavior

The above causes no issue and also compiles without using Artifact = ....

Actual Behavior

An error about Artifact in global-namespace is raised.

Regression?

Yes, worked fine in NUKE v7.0.6 as it referenced Octokit v5 which had no such issues.

Known Workarounds

Reference Octokit directly with <PackageReference Include="Octokit" Aliases="OctokitNs" />

Could you help with a pull-request?

No

[amis92]

@matkoch can you possibly shed a bit more light as to the closing of this issue? It's a transient dependency that NUKE pulls in and prevents people from using their own Artifact type in their scripts.