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

Bump node-jose and @decentralized-identity/sidetree #16

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 16, 2023

Removes node-jose. It's no longer used after updating ancestor dependency @decentralized-identity/sidetree. These dependencies need to be updated together.

Removes node-jose

Updates @decentralized-identity/sidetree from 0.6.1 to 1.0.6

Release notes

Sourced from @​decentralized-identity/sidetree's releases.

Sidetree spec v1.0.0

No release notes provided.

v0.9.1

Fork status: Not a fork*

v0.9.1 Code change Persistent Store Breaking Configuration Change
Core service Yes No* No
Bitcoin microservice No No No
IPFS microservice No No No

*This release technically is a soft fork, but since we anticipate minimal impact, we release this version as a patch.

Core service

  1. Handled the initial case where no general/auth keys are present in a Document.

v0.9.0

Fork status: Hard fork

v0.9.0 Code change Persistent Store Breaking Configuration Change
Core service Yes Yes No
Bitcoin microservice No No No
IPFS microservice No No No

This release breaks backwards compatibility for Core service. Requires DB reset for Core service.

Core service

  1. Renamed usage to purpose for public keys.
  2. Update commit-reveal scheme aligns with recovery commit-reveal scheme.

v0.8.0

Fork status: Hard fork

v0.8.0 Code change Persistent Store Breaking Configuration Change
Core service Yes Yes No
Bitcoin microservice Yes Yes No
IPFS microservice No No No

This release breaks backwards compatibility for Core and Bitcoin services. Requires DB reset for Core and Bitcoin service.

Core service

  1. Changed anchor string format.
  2. Changed DID unique suffix generation algorithm.
  3. Removed the need for recovery reveal values.
  4. Used commit-reveal chain as operation order instead of strict ledger time.
  5. Fixed property casing in operation delta schema.
  6. Allowed any key type for non-operation keys.

... (truncated)

Changelog

Sourced from @​decentralized-identity/sidetree's changelog.

1.0.6 (2022-06-08)

Bug Fixes

  • ref-imp: #1015 - Set deactivated metadata property (151be6f)
  • ref-imp: #1169 - fixed bug on commit-reveal chain leading to infinite loop in resolution (156df5f)
  • ref-imp: added support for IPFS v0.11 (a196c52)
  • ref-imp: allow Bitcoin Core to remember list of wallet to load during startup (#1164) (23d726e)
  • ref-imp: fix deactivate (#1149) (6322ef2)
  • ref-imp: fixed an integer precision bug in how transaction number is constructed (c19a1ec)
  • ref-imp: fixed casing that prevented filtering out mongo commands in logs (d0c42d8)
  • ref-imp: fixed run time crashing of Core due to previous mongodb logging commit (5c0c7f9)
  • ref-imp: fixes controller property to have a value (83ef023)
  • ref-imp: fixing/removing dependencies with known vulnerabilities (6099613)
  • ref-imp: integrate custom logger with mongodb (#1157) (a357828)
  • ref-imp: port transaction processor fix to v1 folder (19c9492)
  • ref-imp: refactored getWriterValueTimeLock() to handle error better (6f9b4d5)
  • ref-imp: updated bitcoin service to retry on connectivity issues (2fe9c78)

BREAKING CHANGES

  • ref-imp: The controller is no longer an empty string and instead matches the document id property (e.g. the did being resolved)

1.0.5 (2021-07-26)

Bug Fixes

  • ref-imp: fix deactivate (#1149) (6322ef2)
  • ref-imp: port transaction processor fix to v1 folder (0b8c1ff)

1.0.4 (2021-07-16)

Bug Fixes

  • ref-imp: automatically create bitcoin wallet (#1138) (674d753)
  • ref-imp: fixed bug where transaction is skipped if save for retry fails (ce23a61)
  • ref-imp: fixed retry logic always fails due to missing fee and lock info (3e16be4)
  • ref-imp: listunspent needs to be a wallet RPC call (ef4ea65)
  • ref-imp: make bitcoin load wallet and specify wallet (#1140) (81e74d1)

... (truncated)

Commits
  • 006e03e chore(ref-imp): official release
  • a196c52 fix(ref-imp): added support for IPFS v0.11
  • 50c9b18 ci(ref-imp): added code coverage badge
  • 95fa462 Remove unnecessary port in config model (#1186)
  • d55ab60 Fix undefined when calculating normalized fee
  • c2eacb0 Added appendix with DHS references and disclaimers (#1133)
  • 7b534ad Removing minConfirmationBetweenWrites (#1179)
  • 62accbc Wait for 6 blocks after last transaction confirmation before writting another...
  • 151be6f fix(ref-imp): #1015 - Set deactivated metadata property
  • becc264 Add id for max operation count (#1166)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by ci_identity_foundation, a new releaser for @​decentralized-identity/sidetree since your current version.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Removes [node-jose](https://github.com/cisco/node-jose). It's no longer used after updating ancestor dependency [@decentralized-identity/sidetree](https://github.com/decentralized-identity/sidetree). These dependencies need to be updated together.


Removes `node-jose`

Updates `@decentralized-identity/sidetree` from 0.6.1 to 1.0.6
- [Release notes](https://github.com/decentralized-identity/sidetree/releases)
- [Changelog](https://github.com/decentralized-identity/sidetree/blob/master/CHANGELOG.md)
- [Commits](decentralized-identity/sidetree@v0.6.1...v1.0.6)

---
updated-dependencies:
- dependency-name: node-jose
  dependency-type: indirect
- dependency-name: "@decentralized-identity/sidetree"
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants