Skip to content

Commit the strong-name key - #14

Merged
Darkseal merged 1 commit into
masterfrom
strong-name-key
Oct 10, 2026
Merged

Darkseal merged 1 commit into
masterfrom
strong-name-key

Conversation

@Darkseal

Copy link
Copy Markdown
Collaborator

The strong-name key (Key.snk) is now part of the repository, as Microsoft recommends for open-source projects: every build, local or CI, produces the same assembly identity.

Key.snk is now tracked, as Microsoft recommends for open-source projects (a strong name
provides identity, not security): local and CI builds share the same assembly identity.
The build no longer generates a key when it is missing, and the release workflow no longer
needs a secret for it.
Copilot AI balanced review requested due to automatic review settings October 10, 2026 17:45

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Approval recommended

The committed key is structurally valid and all build, CI, ignore, and documentation changes are consistent.

0 open findings

What changed in this PR

Commits the strong-name key so local and CI builds produce assemblies with consistent identity.

Changes:

  • Adds and documents the repository-owned Key.snk.
  • Removes local key generation and CI secret restoration.
  • Updates release notes and ignore rules.
File Description
Key.snk Adds the strong-name key.
.gitignore Allows the key to be tracked.
SourceControlSwitcher/​SourceControlSwitcher.csproj Removes fallback key generation.
.github/​workflows/​release.yml Uses the committed key during releases.
BUILD.txt Documents the key’s purpose.
CHANGELOG.txt Records the assembly identity change.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@Darkseal
Darkseal merged commit f000bd3 into master Oct 10, 2026
2 checks passed
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