Package signing key expired; NuGet release failed as a result

[GLM-FM]

Package signing seems to have broken since the previous release, so this version did not end up on NuGet: https://github.com/dotnet/Silk.NET/actions/runs/20318115842/job/58371196747

AADSTS7000222: The provided client secret keys for app '***' are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds.

Originally posted by @GLM-FM in #2489 (comment)

[dos-ise]

Any updates on this? Would like to upgrade to 2.23

[mihai-ene-public]

I'm also interested in this version because it potentially fixes some bugs regarding animation when importing fbx

[KeatonTheBot]

You can install 2.23 by adding the Silk.NET GitLab package registry to nuget.config with the following key: https://gitlab.com/api/v4/projects/51457475/packages/nuget/index.json

The registry itself is here. I'd estimate that 2.23.0, 2.23.0-build5228.0, and the latest "prerelease" are functionally similar, but it would probably be best to use 2.23.0.

[mihai-ene-public]

@KeatonTheBot can't believe I'm replying to a bot but here it goes:
do you think it should be embarrassing for M$ that for more than 2 weeks their signing certificate expired and they couldn't make release for a nuget version, just for the mere reason that they couldn't sign a package ?!?

[KeatonTheBot]

@KeatonTheBot can't believe I'm replying to a bot but here it goes: do you think it should be embarrassing for M$ that for more than 2 weeks their signing certificate expired and they couldn't make release for a nuget version, just for the mere reason that they couldn't sign a package ?!?

Yeah, sounds right to me. Silk.NET is part of the dotnet org (Microsoft), so I'm sure the packages have to be correctly signed in order to upload to nuget.org (also Microsoft).

I'm not a bot, despite the name 😉. I'm the maintainer for Kenji-NX, and I've pushed 2.23 to my repo. This is their official GitLab package registry, so it's a viable alternative.