Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update .snk file for strong naming #805

Merged
merged 1 commit into from
Dec 7, 2023
Merged

Conversation

96malhar
Copy link
Contributor

Issue #, if available:
DOTNET-7248

Description of changes:

  • Updated the .snk file that is used for strong naming.
  • Verified that all projects build correctly and the resulting assemblies are strong-named with the expected public key token.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Copy link

codecov bot commented Nov 18, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c706a13) 61.46% compared to head (2ffdf87) 61.46%.
Report is 3 commits behind head on dev.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #805   +/-   ##
=======================================
  Coverage   61.46%   61.46%           
=======================================
  Files         277      277           
  Lines       10659    10659           
  Branches     1484     1484           
=======================================
  Hits         6552     6552           
  Misses       3566     3566           
  Partials      541      541           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@96malhar 96malhar merged commit 8990861 into dev Dec 7, 2023
11 checks passed
@96malhar 96malhar deleted the kmalhar/update-snk-file branch December 7, 2023 05: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.

3 participants