Skip to content

re-enable signing validation #15593

Closed

Description

@nohwnd

Once issues on arcade side is solved, re-enable validation to make sure everytyhing is correct. This has no impact on how we sign the code, just ensures that we signed correctly #15592

Activity

  1. nohwnd commented on Jun 28, 2026

    @nohwnd
    MemberAuthor

    Triage Analysis 🔍

    The current state of signing validation in azure-pipelines-official.yml:

    - template: eng/common/templates-official/post-build/post-build.yml@self
      parameters:
        # Temporarily skip validation until infra issues are resolved, based on advice from Arcade.
        enableSigningValidation: false

    The arcade SDK has since been updated from the version in use when this was disabled (March 2026) to Microsoft.DotNet.Arcade.Sdk 11.0.0-beta.26310.1 (current in global.json). This is a significant version bump.

    Suggested action: Try re-enabling enableSigningValidation: true in azure-pipelines-official.yml and see if a CI build succeeds. If the arcade infrastructure issues have been resolved, validation should pass. If it still fails, the arcade SDK team should be contacted for status.

    The one-line change to attempt is:

    -        enableSigningValidation: false
    +        enableSigningValidation: true

    🔍 Triaged by Issue Repro Triage & Auto-Fix 🔍

    🔍 Triaged by Issue Repro Triage & Auto-Fix 🔍

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

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions