fix: bump dmk versions, fix minor bugs, autogen signer types#3
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR bumps DMK dependencies to the latest compatible versions, fixes several minor bugs uncovered during integration and testing, and adds auto-generated signer types to improve type safety and developer experience.
Motivation and Context
Keeping DMK dependencies up to date ensures compatibility with recent ecosystem changes and reduces maintenance overhead.
During the upgrade, a few minor issues were identified and fixed.
Auto-generating signer types eliminates manual type definitions, reduces the risk of inconsistencies, and improves correctness when working with signers.
Related Issue
PR fixes the following issue: See the comments
Type of change