Skip to content

Strong-name sign .NET SDK - #1778

Merged
stephentoub merged 1 commit into
mainfrom
stephentoub-dotnet-strong-name
Jun 23, 2026
Merged

Strong-name sign .NET SDK#1778
stephentoub merged 1 commit into
mainfrom
stephentoub-dotnet-strong-name

Conversation

@stephentoub

Copy link
Copy Markdown
Collaborator

The .NET SDK assembly was not being strong-name signed, which can block consumers that require strong-named dependencies.

This enables signing for GitHub.Copilot.SDK using the canonical .NET Open.snk key and keeps the .NET-specific key under the dotnet directory. The resulting SDK assemblies use public key token cc7b13ffcd2ddd51, matching the .NET open-source strong-name key.

Validation:

  • dotnet build dotnet\src\GitHub.Copilot.SDK.csproj -v minimal

Use the canonical .NET Open.snk key to strong-name sign the GitHub.Copilot.SDK assembly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 23, 2026 20:26
@stephentoub
stephentoub requested a review from a team as a code owner June 23, 2026 20:26

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR enables strong-name signing for the .NET SDK assembly (GitHub.Copilot.SDK) so it can be consumed by environments that require strong-named dependencies, using the canonical Open.snk key under the dotnet/ directory.

Changes:

  • Turn on strong-name signing for the GitHub.Copilot.SDK project via Directory.Build.props.
  • Configure the project to use dotnet/Open.snk as the AssemblyOriginatorKeyFile when building that assembly.
Show a summary per file
File Description
dotnet/Directory.Build.props Adds a project-scoped MSBuild property group enabling strong-name signing for GitHub.Copilot.SDK using dotnet/Open.snk.

Copilot's findings

  • Files reviewed: 1/2 changed files
  • Comments generated: 0

@github-actions

Copy link
Copy Markdown
Contributor

Cross-SDK Consistency Review ✅

This PR adds strong-name signing to the .NET SDK — a .NET-specific assembly concept. Strong-name signing has no equivalent in the other SDK implementations (Node.js/TypeScript, Python, Go, Java, Rust), so this change does not create any cross-language consistency gaps.

No action required in other SDKs.

Generated by SDK Consistency Review Agent for issue #1778 · sonnet46 408.9K ·

@stephentoub
stephentoub merged commit 6ec8035 into main Jun 23, 2026
19 checks passed
@stephentoub
stephentoub deleted the stephentoub-dotnet-strong-name branch June 23, 2026 20:46
edburns pushed a commit that referenced this pull request Aug 4, 2026
Use the canonical .NET Open.snk key to strong-name sign the GitHub.Copilot.SDK assembly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
edburns pushed a commit that referenced this pull request Aug 4, 2026
Use the canonical .NET Open.snk key to strong-name sign the GitHub.Copilot.SDK assembly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants