Skip to content

build: pin assembly identity policy - #271

Merged
thomhurst merged 1 commit into
mainfrom
issue-188-strong-naming
Aug 24, 2026
Merged

build: pin assembly identity policy#271
thomhurst merged 1 commit into
mainfrom
issue-188-strong-naming

Conversation

@thomhurst

Copy link
Copy Markdown
Owner

Closes #188.

Decision

Kevlar remains intentionally unsigned for 1.x. Reservoir 1.4.0 is unsigned, and .NET Framework strong naming is viral: signing Kevlar while retaining that dependency is not a valid supported configuration. The limitation and major-release migration boundary are now explicit in the library-author docs.

Behavior

  • pins AssemblyVersion to <package-major>.0.0.0
  • keeps FileVersion at the numeric package version
  • keeps InformationalVersion at full SemVer plus commit
  • verifies all packed assemblies remain unsigned and carry the exact version policy

Microsoft guidance: https://learn.microsoft.com/dotnet/standard/library-guidance/strong-naming

Validation

  • dotnet build Kevlar.slnx -c Release -p:Version=1.2.3-alpha.4 -p:CI=true
  • core tests: 845 passed
  • integration tests: 131 passed
  • analyzer tests: 78 passed
  • Testing tests: 51 passed
  • Chaos tests: 33 passed
  • rate-limiting tests: 24 passed
  • allocation tests: 3 passed
  • netstandard tests: 10 + 4 passed
  • pwsh scripts/Verify-Docs.ps1
  • npm run build in docs/
  • package identity checks passed for all eight packages; full verification then hit the existing gRPC symbol-manifest mismatch addressed by fix(tests): use FallbackTo in new tests #258

@coderabbitai

coderabbitai Bot commented Aug 24, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: bb31638a-a917-4353-a444-9319b2011cff


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@thomhurst
thomhurst force-pushed the issue-188-strong-naming branch 2 times, most recently from 4666df7 to 5156544 Compare August 24, 2026 21:57

@chatgpt-codex-connector chatgpt-codex-connector Bot 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5156544a30

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread scripts/Verify-Packages.ps1
Keep AssemblyVersion stable within each package major while preserving
floating file and informational versions.

Strong naming remains deliberately disabled because the netstandard core
depends on unsigned Reservoir.

Closes #188
@thomhurst
thomhurst force-pushed the issue-188-strong-naming branch from 5156544 to 89f1cd2 Compare August 24, 2026 22:02
@thomhurst
thomhurst merged commit be79db7 into main Aug 24, 2026
9 checks passed
@thomhurst
thomhurst deleted the issue-188-strong-naming branch August 24, 2026 22:16
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.

build(packaging): decide strong naming and pin AssemblyVersion to the major before 1.0

1 participant