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

feat: use did:key as default method for Subject identifier #5

Merged
merged 1 commit into from
Apr 5, 2024

Conversation

nanderstabel
Copy link
Contributor

Description of change

Please write a summary of your changes and why you made them.

Links to any relevant issues

Be sure to reference any related issues by adding fixes issue #.

How the change has been tested

Describe the tests that you ran to verify your changes.
Make sure to provide instructions for the maintainer as well as any relevant configurations.

Definition of Done checklist

Add an x to the boxes that are relevant to your changes.

  • I have followed the contribution guidelines for this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

@nanderstabel nanderstabel force-pushed the feat/did-key-as-default-identifier branch 2 times, most recently from 34d0785 to 5071a79 Compare April 5, 2024 13:22
@daniel-mader daniel-mader changed the title Feat/did key as default identifier feat: use did:key as default method for Subject identifier Apr 5, 2024
@nanderstabel nanderstabel force-pushed the feat/did-key-as-default-identifier branch from 5071a79 to 23308ad Compare April 5, 2024 13:44
@nanderstabel nanderstabel marked this pull request as ready for review April 5, 2024 13:44
@nanderstabel nanderstabel merged commit 2765aca into dev Apr 5, 2024
1 check passed
@nanderstabel nanderstabel deleted the feat/did-key-as-default-identifier branch April 5, 2024 13:48
Copy link

🎉 This issue has been resolved in version 1.0.0-beta.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants