veramolabs / ens-did-resolver Goto Github PK

Prerequisites

Please answer the following questions for yourself before submitting an issue.

• [ x] I am running the latest version
• [ x] I checked the documentation and found no answer
• [x ] I checked to make sure that this issue has not already been filed

Current Behavior

C:\Users\richb\Projects\ens-did-resolver\src\helpers.ts
1:10 warning 'VerificationMethod' is defined but never used @typescript-eslint/no-unused-vars

Expected Behavior

verificationMethod is properly taken from org.w3c.did.verificationMethod in ENS TEXT if present

Failure Information

Please help provide information about the failure.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. run yarn package
2. watch the build
3. Run the resolver on did:ens:fhirfly.eth
4. verificationMethod is not constructed from TEXT key.

Environment Details

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

Failure Logs/Screenshots

Please include any relevant log snippets or files here.
Create a GIST which is a paste of your full or sanitized logs, and link them here.
Please do NOT paste your full logs here, as it will make this issue very long and hard to read!

Alternatives you considered

Please provide details about an environment where this bug does not occur.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://[secure]@github.com/veramolabs/ens-did-resolver.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀

Add ens-did-resolver to existing Veramo DID Driver, and re-submit to DIF, to get did:ens added to Universal Resolver Dev tool

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update devdeps (@babel/core, @babel/preset-env, @babel/preset-typescript, prettier, typescript)
• chore(deps): update devdeps (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-plugin-jest, semantic-release)

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

v0.2.0 did:ens