1210.0.0

@metamask/authenticated-user-storage 3.0.2

Changed

• Bump @metamask/superstruct from ^3.1.0 to ^3.4.1 (#9754)
• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)

@metamask/base-data-service 1.0.0

Added

• Add support for cache persistence (#9445)
  • Persistence can be configured by passing a persistenceConfig option to the constructor.
• Add createServicePolicy and related symbols, copied from @metamask/controller-utils (#9418)
  • Added functions:
    createServicePolicy
  • Added constants:
    • DEFAULT_CIRCUIT_BREAK_DURATION
    • DEFAULT_DEGRADED_THRESHOLD
    • DEFAULT_MAX_CONSECUTIVE_FAILURES
    • DEFAULT_MAX_RETRIES
  • Added types:
    • CreateServicePolicyOptions
    • ServicePolicy
  • Added re-exports from cockatiel:
    • BrokenCircuitError
    • CircuitState
    • CockatielEventEmitter
    • CockatielEvent
    • CockatielFailureReason
    • ConstantBackoff
    • ExponentialBackoff
    • handleAll
    • handleWhen
• Export types DataServiceActions and DataServiceEvents (#9475)
• Add responseStruct option to fetchQuery and fetchInfiniteQuery for validating query responses using Superstruct (#9540)
  • When provided, the struct is used to validate the response and for inferring the return type of the query

Changed

• BREAKING: Remove TPageData type parameter from invalidateQueries method (#9526)
  • This is technically a breaking change, but this was not used in any of our codebases
• BREAKING: Bump @tanstack/query-core from ^4.43.0 to ^5.62.16 (#9712)
  • The option types accepted by fetchQuery, fetchInfiniteQuery, and invalidateQueries now follow the query-core v5 API. Subclasses need to rename cacheTime to gcTime.
  • fetchInfiniteQuery now requires initialPageParam and getNextPageParam, matching query-core's options for infinite queries. This also lets TPageParam be inferred instead of spelled out in the type parameters.
• BREAKING: fetchQuery and fetchInfiniteQuery now take one more type parameter: TDataStruct is the third parameter and the others have been shifted up (#9540)
• BREAKING: Improve type safety of constructor by ensuring the messenger has required actions/events (#9525)
  • No change needed, unless the messenger being passed into the constructor was typed incorrectly.
• Bump @metamask/utils from ^11.9.0 to ^11.11.0 (#9074)
• Bump @metamask/controller-utils from ^12.1.0 to ^12.3.0 (#9058, #9083, #9218)
• Bump @metamask/messenger from ^1.2.0 to ^2.0.0 (#9392)
• Add dependency cockatiel (^3.1.2) (#9418)

@metamask/chomp-api-service 4.0.1

Changed

• Bump @metamask/superstruct from ^3.1.0 to ^3.4.1 (#9754)
• Bump @tanstack/query-core from ^4.43.0 to ^5.62.16 (#9712)
• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)

@metamask/claims-controller 0.6.1

Changed

• Bump @tanstack/query-core from ^4.43.0 to ^5.62.16 (#9712)
• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)

@metamask/money-account-api-data-service 0.4.1

Changed

• Bump @metamask/superstruct from ^3.1.0 to ^3.4.1 (#9754)
• Bump @tanstack/query-core from ^4.43.0 to ^5.62.16 (#9712)
• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)

@metamask/money-account-balance-service 2.4.3

Changed

• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)
• Bump @metamask/money-account-api-data-service from ^0.4.0 to ^0.4.1 (#9972)

@metamask/react-data-query 1.0.0

Changed

• BREAKING: Upgrade @tanstack/query-core and @tanstack/react-query from ^4.43.0 to ^5.62.16 (#9563, #9941, #9953)
  • createUIQueryClient's invalidateQueries override now matches the TanStack Query v5 signature (filters, options) instead of the v4 overload style that relied on parseFilterArgs.
  • Consumers must migrate to TanStack Query v5 APIs (for example gcTime instead of cacheTime, and initialPageParam for infinite queries).
  • TError in both hooks now defaults to DefaultError.
• BREAKING: Constrain createUIQueryClient's messenger-like type to match the given data services (#9475)
  • The messenger-like object that createUIQueryClient takes must minimally support actions or :cacheUpdated:${hash} events which are namespaced by the provided data service names.
  • If you're passing a messenger, it should "just work" as long as your messenger supports the right actions and events.
  • If you're passing a messenger adapter defined in its own variable, you may need to update its type. See MessengerAdapter in packages/react-data-query/src/createUIQueryClient.ts for an example.
  • If you're passing a messenger adapter directly (it is not defined in its own variable), then it should also "just work".
• The types for createUIQueryClient no longer check that the provided messenger's actions are JSON-compatible (#9475)
  • If you are experiencing any errors calling actions through the query client, check to make sure their parameters are JSON-compatible.
• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)

@metamask/sample-controllers 5.0.6

Changed

• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)

@metamask/sentinel-api-service 1.0.1

Changed

• Bump @metamask/superstruct from ^3.1.0 to ^3.4.1 (#9754)
• Bump @tanstack/query-core from ^4.43.0 to ^5.62.16 (#9712)
• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)

@metamask/shield-controller 6.0.1

Changed

• Bump @metamask/transaction-controller from ^69.5.1 to ^69.6.1 (#9823, #9960, #9969)
• Bump @tanstack/query-core from ^4.43.0 to ^5.62.16 (#9712)
• Bump @metamask/signature-controller from ^39.2.9 to ^39.2.10 (#9969)
• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)

@metamask/social-controllers 2.7.2

Changed

• Bump @metamask/superstruct from ^3.1.0 to ^3.4.1 (#9754)
• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)

@metamask/subscription-controller 8.0.1

Changed

• Bump @tanstack/query-core from ^4.43.0 to ^5.62.16 (#9712)
• Bump @metamask/transaction-controller from ^69.5.2 to ^69.6.1 (#9960, #9969)
• Bump @metamask/base-data-service from ^0.1.3 to ^1.0.0 (#9972)