Skip to content

Releases: spruceid/ssx

ssx-react/v1.1.0

08 Dec 16:07
6f2be75
Compare
Choose a tag to compare

Minor Changes

  • 1c685c8: This allows a for different web3 providers to be passed to the ssx-react instance. It still uses wagmi.sh as the default provider if none is passed.

Patch Changes

  • c989838: Refactor code to avoid duplication and improve performance.

    • Updates ssxConfig?: SSXConfig; on SSXProviderProps to ssxConfig?: SSXClientConfig; (non breaking change).
  • Updated dependencies [c989838]

  • Updated dependencies [c66f308]

  • Updated dependencies [83c314c]

ssx-gnosis-extension/v1.1.0

08 Dec 16:07
6f2be75
Compare
Choose a tag to compare

1.1.0

Minor Changes

  • c989838: Refactor code to avoid duplication and improve performance.

    • Adds @spruceid/ssx-core as a dependency;
    • Adds types from ssx-core to all SSX related variables;
    • Optimizes try/catch blocks.
  • Updated dependencies [c989838]

  • Updated dependencies [83c314c]

ssx-core/v1.0.0

08 Dec 16:04
6f2be75
Compare
Choose a tag to compare

SSX Core v1.0.0

We're excited to announce the first release of SSX Core, a package holds the core types, commonly reused components and logic throughout SSX. This package helps us write better, more testable and maintainable code.

What's New

Major Changes

  • c989838: Refactor code to avoid duplication and improve performance.
    • This package was created to held the types definitions and utils functions to all packages. This reduces the amount of duplicated code, prevent circular dependencies, reduces package sizes (tree-shaking during transpilation), and ensures that changes to the API will need a bump to this new package.
    • To unify the packages some interfaces/types names were updated:
      • @spruceid/ssx-sdk: SSXConfig -> SSXClientConfig;
      • @spruceid/ssx-sdk: SSXProviders -> SSXClientProviders;
      • @spruceid/ssx-sdk: SSXSession -> SSXClientSession;
      • @spruceid/ssx-server: SSXConfig -> SSXServerConfig;
      • @spruceid/ssx-server: SSXProviders -> SSXServerProviders;

Minor Changes

  • 83c314c: Enable custom paths for endpoints on client and server.
    • Creates and exports SSXServerRoutes interface
    • Adds routes?: SSXServerRoutes to SSXClientConfig.providers.server.

ssx-sdk/v1.0.0

15 Nov 18:22
ffa2132
Compare
Choose a tag to compare

Major Changes

  • f317c82: Public release of the SSX SDK

Minor Changes

  • a91af88: Throws an error in case an API is configured but no nonce is returned from it.
  • 1072382: Add ENS resolution feature to the client and server to allow the developer to choose where to resolve it.
    • Adds ENS resolution configuration when creating a new SSX instance. This configuration isn't mandatory;
    • Updates SSXSession interface to add ens: SSXEnsData as optional property;
    • Updates ssx.signIn() to resolve ENS data according to the SSX config. This method now sends resolveEns param to the /ssx-login request;
    • Adds ssx.resolveEns(...) method to resolve ENS data on client;
    • The internal SSX session object is now public and accessible by ssx.session;
    • Updates ssx-test-dapp to conform with the latest changes.

Patch Changes

  • Updated dependencies [f317c82]
  • a44f78c: Detect wallet connection and prevent connect attempt if already connected
  • 0f84d97: Detect if a web3 provider is being provided instead of always instantiating a new Web3Provider.

ssx-serverless/v1.0.0

15 Nov 18:21
ffa2132
Compare
Choose a tag to compare

Major Changes

  • f317c82: Public release of the SSX SDK

Patch Changes

  • 1072382: Add ENS resolution feature to the client and server to allow the developer to choose where to resolve it.

    • Updates the ENS resolution to only return defined properties.
  • Updated dependencies [f317c82]

ssx-server/v1.0.0

15 Nov 18:21
ffa2132
Compare
Choose a tag to compare

Major Changes

  • f317c82: Public release of the SSX SDK

Minor Changes

  • 1072382: Add ENS resolution feature to the client and server to allow the developer to choose where to resolve it.
    • Adds ssx.resolveEns(...) method to resolve ENS data;
    • Express and HTTP middlewares /ssx-login responses were updated. These requests were returning a session object with a session property. Now it returns a session object without the session property, but keeping all information;
    • Updates ssx-test-express-api and ssx-test-http-api to conform with the latest changes.

Patch Changes

ssx-react/v1.0.0

15 Nov 18:22
ffa2132
Compare
Choose a tag to compare

Major Changes

  • f317c82: Public release of the SSX SDK

Patch Changes

ssx-gnosis-extension/v1.0.0

15 Nov 18:20
ffa2132
Compare
Choose a tag to compare

Purpose

spaceIds now will be used for delegation. For SIWE spaceIds are keccak256("siwe" + delegate.address). This allows for multi-delegation per Safe.

Resolution

Updated event filters to instead of filter only by delegate.address to also filter by spaceIds.

End-User Impact

Delegations made outside the new space will not be displayed.

Support Impacts

All delegations will need to be re-made under the new spaceId

Major Changes

  • f317c82: Public release of the SSX SDK

create-ssx-dapp/v1.0.0

15 Nov 18:19
ffa2132
Compare
Choose a tag to compare

Major Changes

  • f317c82: Public release of the SSX SDK

ssx-sdk/v0.1.1

09 Nov 18:52
ba9ef73
Compare
Choose a tag to compare

Overview

This updates the ssx-sdk to give more context and flexibility to the ssx-powered server when manipulating the session.

Purpose

ssx-sdk getNonce, signIn and signOut requests send more parameters to the ssx-powered server to give more context and flexibility when manipulating the session.

Resolution

We added more parameters to the requests as follow:

  • GET /ssx-nonce now passes address, chainId, domain and issuedAt as query parameters
  • POST /ssx-login and /ssx-logout now passes all session information (siwe, signature, address, walletAddress, chainId and daoLogin) as body

Developer Impacts

  • Developers can now pass instantiated web3Providers to SSX

End-User Impact

  • Users will no longer be prompted to connect if they have already connected their wallet to the site

Support Impacts

None