> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/changelog/release-note/2025/q3-2025.md).

# Q3 2025

Release notes for July to September 2025.

{% updates format="full" %}
{% update date="2025-09-29" %}

## 0.5.3148

* Implemented heuristic Freshness Cache (RFC 7234 §4.2.2) for external images while building passes.
  {% endupdate %}

{% update date="2025-09-28" %}

## 0.5.3141

* Fixed pass preview layout triggering the pass data provider twice.
* Fixed UTM parameters sometimes being lost with custom ID parameters.
* Updated the “Powered by” icon to The Wallet Crew logo.
  {% endupdate %}

{% update date="2025-09-27" %}

## 0.5.3134

* Added a `sleep` method for custom scripts.
* Added an early version of the pass history page.
* Allowed cancelling mass push update operations.
* Added a new Logs dashboard, replacing Elastic and adding translations.
  {% endupdate %}

{% update date="2025-09-25" %}

## 0.5.3123

* Added autocomplete in metadata values on the new pass dashboard.
* Added a new logs page. Logs are retained for 45 days.

<figure><img src="https://2425106641-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FohFVLgeDoRJUI1NJz3Js%2Fuploads%2Fgit-blob-a97dc80c17f1f35771e247b90561a39ce95dbd98%2Fresources-release-note-new-logs%20(1).png?alt=media" alt="New logs page"><figcaption><p>The new logs page: check the platform log lines, retained for 45 days.</p></figcaption></figure>
{% endupdate %}

{% update date="2025-09-19" %}

## 0.5.3101

* Added `claimType` in `tokenGenerator`.
* Fixed Stripo email editor not allowing editing block properties.
* Added UI to configure the default pass type for Secutix.
* Added installation source in `runtime.wallet.passUpdater` custom endpoint.
  {% endupdate %}

{% update date="2025-09-18" %}

## 0.5.3095

* Klaviyo `SynchronizeProfile` now uses a queue.
  {% endupdate %}

{% update date="2025-09-15" %}

## 0.5.3084

* Added Liquid support in Google templates for `validtimeinterval` and balance update time fields.
* Improved accessibility in the customer registration form.
* Added debug info for Cegid Y2 providers.
* Added unique IDs and aria labels to form fields and buttons.
* Improved date selector structure with roles and labels.
* Introduced a semantic tag to clarify the primary content area.
* Refined hover and focus feedback for high-contrast mode.
* Fixed an issue in Google Wallet when template names contain invalid characters.
* Improved newline rendering for multi-line fields in the template editor.
* Centralized push updates into a single modal.
* Added bulk update to pass list with throughput control and labels.
* Removed deprecated Event API in favor of Insights API.
* Added a new home page.
* Added a new wallet dashboard.
  {% endupdate %}

{% update date="2025-09-03" %}

## 0.5.3029

* Added `runtime.emailAccountChallenger.templateFinder` to select email templates conditionally.
  {% endupdate %}

{% update date="2025-09-03" %}

## 0.5.3023

* UR connector: ability to list coupons.
* Added source info for the Cinto SDK (tags, medium, origin).
* Added a new accessibility-friendly modal for the Cinto SDK.
  {% endupdate %}

{% update date="2025-08-29" %}

## 0.5.3000

* Applied templating for currency code in Gift Card template preview (Google).
* Added `installCount` to `Pass:Installed` and `Pass:Uninstalled` events.
* Fixed Google registration count with multiple installation accounts.
  {% endupdate %}

{% update date="2025-08-27" %}

## 0.5.2979

* Added conditions on the actual `storeId` used by the app (vendor layout).
  {% endupdate %}

{% update date="2025-08-20" %}

## 0.5.2966

* Implemented email lookup within UR connector.
* Added `onUserNotFoundOptions` in `PreRegisterBehavior`.
* Patch API: added option to set `correlationId` to group nightly batch updates.
  {% endupdate %}

{% update date="2025-08-04" %}

## 0.5.2949

* Added SFTP support to read files. See: [Update pass using flat files](/configure/advanced-configuration/wallet/import-and-export/update-pass-using-flat-files.md)
* Security improvements in Core API.
  {% endupdate %}

{% update date="2025-07-06" %}

## 0.5.2902

* Technical improvements in runtime.
  {% endupdate %}

{% update date="2025-07-03" %}

## 0.5.2889

* Added a new authentication option: send API key using basic authentication.
* Use username `X-API-KEY` and the Neostore API key as password.
  {% endupdate %}

{% update date="2025-07-01" %}

## 0.5.2879

* Added a new audit log when calling the API.
* Google gift card: banner image is now displayed properly.
* Added a new UI to create pass templates.
* Added an option to override the default layout for Google Wallet passes.
* Added support for the GSA (Google Search Assistance) browser.
* Fixed issues with Apple Opera and Cinto SDK.
  {% endupdate %}
  {% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/changelog/release-note/2025/q3-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
