Skip to content

Releases: safe-global/safe-client-gateway

v1.14.0

20 Nov 10:13
84b89ee
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.13.1...v1.14.0

v1.13.1

10 Nov 11:41
9d1cf9e
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.13.0...v1.13.1

v1.13.0

10 Nov 09:46
450c42e
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.12.0...v1.13.0

v1.12.0

07 Nov 10:35
5b7b59b
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.11.1...v1.12.0

v1.11.2

02 Nov 15:09
9b612ca
Compare
Choose a tag to compare

What's Changed

Fix CacheDir for token prices

  • Modifies the CacheDir for token/native coins prices. This prevents subsequent requests from renewing the cache TTL for the entire key.

Full Changelog: v1.11.1...v1.11.2

v1.11.1

31 Oct 14:04
d98ea80
Compare
Choose a tag to compare

What's Changed

Fix get-contract E2E test

  • Adapts get-contract e2e test to the current contract metadata.

Full Changelog: v1.11.0...v1.11.1

v1.11.0

31 Oct 13:05
0cb6de9
Compare
Choose a tag to compare

What's Changed

  • Slice nested transfers by @hectorgomezv in #771

    • Cuts the number of nested transfers for each transaction in the history to a max value.
  • feat: add alerts (Tenderly) data source by @iamacook in #787

    • Adds a new alerts data source, leveraging the Tenderly API in anticipation of Tenderly Alerts for the forthcoming recovery implementation.

Other changes

Full Changelog: v1.10.1...v1.11.0

v1.10.1

24 Oct 14:58
0dcd623
Compare
Choose a tag to compare

What's Changed

Limit the number of nested transactions

The number of nested transactions for the Safe's history is now limited via MAX_NESTED_TRANSFERS. The default value is 100 transactions.

Note: Setting a negative value would still limit the number of transactions but would show the first numberOfTransactions - MAX_NESTED_TRANSFERS (instead of the first MAX_NESTED_TRANSFERS)

Full Changelog: v1.10.0...v1.10.1

v1.10.0

24 Oct 12:03
2700b86
Compare
Choose a tag to compare

What's Changed

  • Set default values for trusted and exclude_spam params by @fmrsabino in #735

    • /balances endpoint trusted query param will be false if none is provided.
    • /balances endpoint exclude_spam query param will be true if none is provided.
  • Change relative import paths to non-relative path aliases by @hectorgomezv in #749

    • Full paths with path aliases are now used on import statements in the whole service codebase.
  • Add external prices provider support by @hectorgomezv in #732

    • This PR adds the option to get token prices from an external prices provider (Coingecko). This feature is behind a feature flag, managed by the environment variable FF_PRICES_PROVIDER_CHAIN_IDS. So including chain IDs into FF_PRICES_PROVIDER_CHAIN_IDS (as comma-separated numbers), will enable Coingecko prices retrieval for those chain IDs.
  • Add RootController with SwaggerUI redirection by @hectorgomezv in #754

    • Redirects the root path to the SwaggerUI web app. This is intended to prevent the service from showing the default SwaggerUI template when requesting the index.html page directly.
  • Add Postgres database integration by @fmrsabino in #760

    • Adds support for connecting to a Postgres database. This is completely optional. It will only result in an error if a query is made and there's no database server running.
  • Allow null values as Safe version by @hectorgomezv in #764

    • Adds support for having null as Safes version attribute. This makes the service compatible with the Safe Transaction Service, which now allows a null version attribute if the masterCopy address is not one of the deterministic known addresses.

Other Changes

Full Changelog: v1.9.0...v1.10.0

v1.9.0

09 Oct 13:03
59ba23d
Compare
Choose a tag to compare

What's Changed

Support for CHAIN_UPDATE and SAFE_APPS_UPDATE hooks

Support was added for two new hook types: CHAIN_UPDATE and SAFE_APPS_UPDATE in #683.

The CHAIN_UPDATE hook invalidates all Chain related data for the specified chain (it also invalidates the paginated response for all the chains).

The SAFE_APPS_UPDATE hook invalidates all Safe Apps related data for the specified chain.

The hooks can be triggered via the /hooks/events endpoint:

POST /v1/hooks/events

{
  "type": "CHAIN_UPDATE" | "SAFE_APPS_UPDATE",
  "chainId": <chainId>,
}

Added support for Safe-App-User-Agent logging

Added support for logging the value of the header Safe-App-User-Agent. #714 This header can be used for analytics regarding the source of the request.

Note: Considerations regarding where the header should be set and respective values are not specified, and we leave that decision for the users running this service.

Other Changes

  • build(deps): bump the nest-js-core group with 4 updates in #717
  • build(deps): bump viem from 1.8.1 to 1.14.0 in #723
  • build(deps): bump @nestjs/cli from 10.1.12 to 10.1.18 in #718
  • build(deps): bump @safe-global/safe-deployments from 1.26.0 to 1.27.0 in #719
  • build(deps): bump rimraf from 5.0.1 to 5.0.5 in #721
  • build(deps-dev): bump eslint from 8.49.0 to 8.50.0 in #724
  • build(deps-dev): bump @types/express from 4.17.17 to 4.17.18 in #726
  • build(deps-dev): bump @typescript-eslint/eslint-plugin from 6.7.0 to 6.7.4 in #722
  • build(deps-dev): bump @typescript-eslint/parser from 6.6.0 to 6.7.3 in #720
  • build(deps-dev): bump @typescript-eslint/parser from 6.7.3 to 6.7.4 in #725

Full Changelog: v1.8.1...v1.9.0