You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need support migrating coverlet package signing from secret/certificate-based authentication to managed identity for dotnet sign.
Background:
We already tracked this in our project: coverlet-coverage/coverlet#1841
Our current signing certificate is approaching the end of its validity period.
We want to complete migration as soon as possible to avoid release disruption and align with the managed identity direction.
Could you please help us with:
The required onboarding steps for managed identity in our signing flow
Any required repository/pipeline details you need from us
Recommended timeline and any constraints we should account for
If helpful, we can provide workflow/pipeline details immediately and test changes quickly.
Thanks a lot for your help and guidance.
Hi team, we wanted to publish a new release today but as expected the secret is now expired. We would love to get the new release out but need some help now to sign it properly.
Activity
daveMueller commentedon Sep 13, 2026
Hi team, we wanted to publish a new release today but as expected the secret is now expired. We would love to get the new release out but need some help now to sign it properly.
cc @MarcoRossignoli, @Bertk
daveMueller commentedon Sep 21, 2026
@clairernovotny can you help out here? Our releases are blocked until this is resolved.
Evangelink commentedon Sep 22, 2026
@ChrisSfanos is having a look
ChrisSfanos commentedon Sep 22, 2026
Ping me at chris.sfanos (at) dotnetfoundation.org and I'll send you the updated secret