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

docs: Introduced breaking changes in Pluto as we are intro… #116

Merged
merged 1 commit into from
Nov 7, 2023

Conversation

elribonazo
Copy link
Contributor

@elribonazo elribonazo commented Nov 7, 2023

We are about to release prism 2.6 and as reported by a user we have missed introducing the breaking change in Pluto. Despite Pluto is not part of our bundle anymore, we do cause disruption with existing users and the correct is to apply the breaking change.

Only positive thing is that 2.5.0 is part of 2.6 prism release which is not yet released, its a draft release.

This PR does not introduce the breaking change but just applies the configuration and doc changes.

  • X25519 keys were wrongly set as EC (elliptic) key types which is wrong. EC25519 + Secp256k1 belong to EC key type, X25519 should have Curve25519 instead to be valid. If you previously had a key stored as EC (x25519) changing that keyType to KeyTypes.X25519 (Curve25519).
  • As we have introduced new credential types we have also built a credential abstraction so storing and fetching credentials becomes easier.

…ducing credential abstraction and anoncred issuing functionality.

- X25519 keys were wrongly set as EC (elliptic) key types which is wrong. EC25519 + Secp256k1 belong to EC key type, X25519 should have Curve25519 instead to be valid. If you previously had a key stored as EC (x25519) changing that keyType to KeyTypes.X25519 (Curve25519).
- As we have introduced new credential types we have also built a credential abstraction so storing and fetching credentials becomes easier.
@elribonazo elribonazo changed the title BREAKING CHANGE: Introduced breaking changes in Pluto as we are intro… docs: Introduced breaking changes in Pluto as we are intro… Nov 7, 2023
Copy link

github-actions bot commented Nov 7, 2023

Lines Statements Branches Functions
Coverage: 41%
36.98% (1545/4177) 24.93% (724/2903) 38.62% (487/1261)

JUnit

Tests Skipped Failures Errors Time
209 2 💤 0 ❌ 0 🔥 51.128s ⏱️

@elribonazo elribonazo marked this pull request as ready for review November 7, 2023 10:38
@elribonazo elribonazo merged commit be8c6e8 into master Nov 7, 2023
8 checks passed
@elribonazo elribonazo deleted the feature/pluto-breaking branch November 7, 2023 11:06
atala-dev added a commit that referenced this pull request Nov 7, 2023
# [3.0.0](v2.5.0...v3.0.0) (2023-11-07)

* docs!: Introduced breaking changes in Pluto as we are intro… (#116) ([be8c6e8](be8c6e8)), closes [#116](#116)

### Features

* **Agent:** add initialize function ([#107](#107)) ([14389a1](14389a1))

### BREAKING CHANGES

* Introduced breaking changes in Pluto as we are introducing credential abstraction and anoncred issuing functionality.
- X25519 keys were wrongly set as EC (elliptic) key types which is wrong. EC25519 + Secp256k1 belong to EC key type, X25519 should have Curve25519 instead to be valid. If you previously had a key stored as EC (x25519) changing that keyType to KeyTypes.X25519 (Curve25519).
- As we have introduced new credential types we have also built a credential abstraction so storing and fetching credentials becomes easier.
github-actions bot pushed a commit that referenced this pull request Nov 7, 2023
# [3.0.0](v2.5.0...v3.0.0) (2023-11-07)

* docs!: Introduced breaking changes in Pluto as we are intro… (#116) ([be8c6e8](be8c6e8)), closes [#116](#116)

### Features

* **Agent:** add initialize function ([#107](#107)) ([14389a1](14389a1))

### BREAKING CHANGES

* Introduced breaking changes in Pluto as we are introducing credential abstraction and anoncred issuing functionality.
- X25519 keys were wrongly set as EC (elliptic) key types which is wrong. EC25519 + Secp256k1 belong to EC key type, X25519 should have Curve25519 instead to be valid. If you previously had a key stored as EC (x25519) changing that keyType to KeyTypes.X25519 (Curve25519).
- As we have introduced new credential types we have also built a credential abstraction so storing and fetching credentials becomes easier.
mixmix pushed a commit to mixmix/atala-prism-wallet-sdk-ts that referenced this pull request May 6, 2024
…dger#116)

BREAKING CHANGE: Introduced breaking changes in Pluto as we are introducing credential abstraction and anoncred issuing functionality.
- X25519 keys were wrongly set as EC (elliptic) key types which is wrong. EC25519 + Secp256k1 belong to EC key type, X25519 should have Curve25519 instead to be valid. If you previously had a key stored as EC (x25519) changing that keyType to KeyTypes.X25519 (Curve25519).
- As we have introduced new credential types we have also built a credential abstraction so storing and fetching credentials becomes easier.

Signed-off-by: Francisco Javier Ribó Labrador <elribonazo@gmail.com>
mixmix pushed a commit to mixmix/atala-prism-wallet-sdk-ts that referenced this pull request May 6, 2024
# [3.0.0](hyperledger/identus-edge-agent-sdk-ts@v2.5.0...v3.0.0) (2023-11-07)

* docs!: Introduced breaking changes in Pluto as we are intro… (hyperledger#116) ([be8c6e8](hyperledger@be8c6e8)), closes [hyperledger#116](hyperledger#116)

### Features

* **Agent:** add initialize function ([hyperledger#107](hyperledger#107)) ([14389a1](hyperledger@14389a1))

### BREAKING CHANGES

* Introduced breaking changes in Pluto as we are introducing credential abstraction and anoncred issuing functionality.
- X25519 keys were wrongly set as EC (elliptic) key types which is wrong. EC25519 + Secp256k1 belong to EC key type, X25519 should have Curve25519 instead to be valid. If you previously had a key stored as EC (x25519) changing that keyType to KeyTypes.X25519 (Curve25519).
- As we have introduced new credential types we have also built a credential abstraction so storing and fetching credentials becomes easier.

Signed-off-by: Francisco Javier Ribó Labrador <elribonazo@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants