docs: release notes for 1.14 #297
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…1.14 merging develop branch.
…1.14 merging develop branch
DennisDyallo
approved these changes
Sep 16, 2025
Collaborator
DennisDyallo
left a comment
DennisDyallo
left a comment
There was a problem hiding this comment.
LGTM, just note my comments. Feel free to merge when ready
|
|
||
| - The SDK has been updated to target .NET Framework 4.7.2, which provides broad reliability, security, and performance improvements. ([#274](https://github.com/Yubico/Yubico.NET.SDK/pull/274)) | ||
|
|
||
| - A ``FailedApdu`` helper method has been added to the ``OtpErrorTransform`` pipeline to streamline the creation of failed APDU responses. Additionally, the sequence validation logic of the ``OtpErrorTransform`` pipeline has been updated to handle edge cases more effectively. ([#276](https://github.com/Yubico/Yubico.NET.SDK/pull/276)) |
Collaborator
There was a problem hiding this comment.
This method is private, so no need to add it to the release notes
|
|
||
| - ``ToString`` overrides have been introduced in the [CommandApdu](xref:Yubico.Core.Iso7816.CommandApdu) and [ResponseApdu](xref:Yubico.Core.Iso7816.ResponseApdu) classes to provide a human-readable string representation of their internal state. These changes improve debugging and logging of APDUs. ([#270](https://github.com/Yubico/Yubico.NET.SDK/pull/270)) | ||
|
|
||
| - A new internal ``HkdfUtilities`` class has been added to the SDK. This class implements HKDF key derivation using HMAC-SHA256, as specified in RFC 5869, providing a reusable and standards-compliant key derivation utility. ([#299](https://github.com/Yubico/Yubico.NET.SDK/pull/299)) |
Collaborator
There was a problem hiding this comment.
This is internal, so it is of no use to the user. I'm wondering if there's any use in including changes that cannot be used by the user? This will lead to lengthy release notes.
Contributor
Author
|
@DennisDyallo Sure, I can remove these for the sake of brevity. They sounded like performance improvements that developers would be interested in hearing about (even if they aren't features they can directly use, like a public method), but if you don't think they are very significant, I can leave them off. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Release notes for 1.14.
How has this been tested?
Local docs build