Giter Club home page Giter Club logo

did-provider-cheqd's People

Contributors

abdulla-ashurov avatar ankurdotb avatar askolesov avatar daevmithran avatar dependabot[bot] avatar eengineer1 avatar jay-dee7 avatar rosspower11 avatar semantic-release-bot avatar snyk-bot avatar

Stargazers

avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar

Forkers

ixofoundation abdulla-ashurov

did-provider-cheqd's Issues

The automated release is failing 🚨

🚨 The automated release from the release/1.0.x 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 release/1.0.x 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:

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.

The release 1.0.1 on branch release/1.0.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.0.0 <1.0.0 can be published from branch release/1.0.x.

The following commit is responsible for the invalid release:

This commit should be moved to a valid branch with git merge or git cherry-pick and removed from branch release/1.0.x with git revert or git reset.

A valid branch could be main.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the 0.0.x 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 0.0.x 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:

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.

The release 1.0.0 on branch 0.0.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.0.0 <0.1.0 can be published from branch 0.0.x.

The following commits are responsible for the invalid release:

  • Remove permissions section (a6162a6)
  • Debug (cc52206)
  • Add repositoryUrl (6f210d7)
  • Move to branch from tags (e5b68ff)
  • Change definition for release tags (a66e33d)
  • Add semantic release (e90639e)
  • Get all the tages back (eb27046)
  • Get version back (2e06426)
  • Debug (ab4c266)
  • Debug (05c9cc6)
  • Add package publishing to github (c606929)
  • ci(security): Add CodeQL security analysis (c233269)
  • Update codeql.yml (90c6137)
  • Fixed CodeQL execution (385cbd0)
  • Add CodeQl (744a0ca)
  • chore: Bump path-parse from 1.0.6 to 1.0.7 (355f486)
  • chore: Bump tmpl from 1.0.4 to 1.0.5 (0f47b67)
  • Bump path-parse from 1.0.6 to 1.0.7 (ff2f0c1)
  • chore: Bump tar from 4.4.13 to 4.4.19 (ecc5846)
  • chore: Bump minimist from 1.2.5 to 1.2.6 (f171b21)
  • Bump tmpl from 1.0.4 to 1.0.5 (8b4d361)
  • Bump tar from 4.4.13 to 4.4.19 (038b0a7)
  • chore: Bump url-parse from 1.5.1 to 1.5.10 (294d47d)
  • Bump minimist from 1.2.5 to 1.2.6 (1a0ebd8)
  • chore(dependencies): Bump express-handlebars from 5.2.0 to 5.3.5 (86d1bba)
  • Merge branch 'dependabot/npm_and_yarn/express-handlebars-5.3.5' of https://github.com/cheqd/did-provider-cheqd into dependabot/npm_and_yarn/express-handlebars-5.3.5 (7ee7053)
  • Bump url-parse from 1.5.1 to 1.5.10 (e94cb2f)
  • Bump express-handlebars from 5.2.0 to 5.3.5 (ee000d1)
  • fix(security): Bump sqlite3 from 5.0.0 to 5.0.8 (79b8984)
  • Bump sqlite3 from 5.0.0 to 5.0.8 (3af1890)
  • refactor: Resolve linter and test issues before taking public [DEV-1337] (683a78b)
  • Add a lot of eslint rules disablings (6f5ddc4)
  • Disable any and unsed vars rules (9cbe7df)
  • Get rid of renovate (980a107)
  • Get rid of another died section (63556c4)
  • Fix README. Get rid of died sections (daaf1c7)
  • Update lint.yml (cc8290a)
  • Updated all linters (7a314ef)
  • Add pull request checker (5a2fefa)
  • Remove CodeQL (6cb959e)
  • Change codeQl (ac705d4)
  • Add CodeQl (f5ca1ed)
  • Fix README lint (fcf9b3f)
  • Fix config paths (f68db16)
  • Get rid of prettier and change lint to Super Linter (84d82d8)
  • Move unit tests into build (bb424a8)
  • Fix linter (aa06b89)
  • Get tests back (6b92202)
  • Remove unused tests (5b61e8d)
  • Comment tests (0380624)
  • Fix build (da3b454)
  • Fix linting and add prettier (102a79c)
  • Merge remote-tracking branch 'origin/latest-did-provider' into prepare_for_public (214175c)
  • Enable lint (cc69745)
  • Add configs for linting (e9028e4)
  • Get rid of frozen-lockfile (d90f117)
  • Add packages (d061971)
  • Return package-lock back (31a61dd)
  • Remove lock file (0f1f108)
  • Remove concurrency (8c10f7b)
  • Debug (8df4373)
  • Add needed plugin (5a7b03a)
  • Fix workflows (8e7c6c6)
  • Add linter and build workflows (54d13e4)
  • feat: add semantic.yml (d10cc05)
  • feat: Add templates .gitignore (1e1db03)
  • Added to reflect latest changes on main repo (38743f7)
  • Update Test workflow to bring inline others (5cd2923)
  • Update test.yml (f1d8bb7)
  • Initialise default files (c2b75be)
  • Bump express-handlebars from 5.2.0 to 5.3.5 (b1808ab)
  • Synced latest resolver improvements (e852c22)
  • Added fixed 32 char length (d874698)
  • Fixed type mismatches (23f52fc)
  • Added base classes & definitions (a666fb7)
  • Initial commit (e05d81f)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 0.0.x with git revert or git reset.

A valid branch could be main.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the release/1.0.x 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 release/1.0.x 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:

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.

The release 1.0.0 on branch release/1.0.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.0.0 <1.0.0 can be published from branch release/1.0.x.

The following commits are responsible for the invalid release:

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch release/1.0.x with git revert or git reset.

A valid branch could be main.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.