> 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/q2-2025.md).

# Q2 2025

Release notes for April to June 2025.

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

## 0.5.2773

* Fixed docs and `additionalData` missing on the `passType` flow element.
* Allowed non-JWT tokens in OAuth2 fetch implementation.
* Fetch improvements to send objects and improve logging.
* Improved Secutix default pass type finder with new extensibility points.
  {% endupdate %}

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

## 0.5.2872

* Added `extensions.secutix.movement.mapper` for non-standard Secutix mapping.
  {% endupdate %}

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

## 0.5.2867

* Added `loyalty.expirationdate` and `loyalty.activationDate` in `Y2CustomerLoyaltyProvider`.
* Fixed push update dialog automatically disappearing.
  {% endupdate %}

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

## 0.5.2862

* Fixed UI issue with `countryStateList` & `countryList` behavior on desktop.
* Avoided displaying “or” in sign-in options when no providers are configured.
  {% endupdate %}

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

## 0.5.2856

* Added validation rules on radio fields.
* Full rewrite of the internal distributed cache.
  {% endupdate %}

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

## 0.5.2830

* Fixed autogenerated docs for the scripting endpoint when large types contain integer enums.
* Added option to bypass server certificates.
* Fixed PDF receipt display for some tenant configurations.
  {% endupdate %}

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

## 0.5.2821

* Added an API to clear cache for a specified tenant.
* Improvements in Cegid UR connector.
* Added product info in `extensions.secutix.ticket.passTypeFinder` extensibility endpoint.
* Fixed store import from Excel files.
* Added a fetch auth provider option for custom token providers.
  {% endupdate %}

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

## 0.5.2789

* Added support for rewards tier & secondary rewards tier in Google loyalty cards.
* Changed the default list display to show rewards tier, then account name.
  {% endupdate %}

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

## 0.5.2784

* Allowed custom domains for Google & Apple pass registration callbacks.
  {% endupdate %}

{% update date="2025-05-26" %}

## 0.5.2765

* Added `OnPassCreating` and `OnPassUpdating` events to scriptable `passUpdater`.
  {% endupdate %}

{% update date="2025-05-21" %}

## 0.5.2759

* Added support for `merchantLocation` in Google Wallet passes.
  {% endupdate %}

{% update date="2025-05-21" %}

## 0.5.2753

* Geo notification configuration now keeps fixed position.
* Authentication now uses the custom domain `auth.neostore.cloud`.
* Swapped longitude/latitude field positions in the store editor.
  {% endupdate %}

{% update date="2025-05-17" %}

## 0.5.2729

* Fixed PDF display issues on some browser versions.
* Reviewed EmailEngine to allow extensibility through JS scripts.
* Added a secret API to share secret-related configuration in Key Vault.
* Added a method to retrieve secrets from scripts.
* Improved API to manage secrets.
  {% endupdate %}

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

## 0.5.2703

* Improved Google Wallet push updates.
* Fixed “update metadata” checkbox always checked.
  {% endupdate %}

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

## 0.5.2701

* Trimmed text field values to ensure non-whitespace values with `required` fields.
  {% endupdate %}

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

## 0.5.2688

* Fixed Add to Wallet button on Ecosia browser for iOS.
* Allowed changing Apple pass type identifiers in back-office.
* Reviewed scheduler retry policy logic.
* Fixed saving Apple configuration.
* Added sorting of scheduler task list by schedule date.
* Fixed email language sent for check-in and deduplication.
* Allowed specifying `additionalData` when creating pass through Flow.
* Improved retry date handling with >10k messages in scheduler.
* Fixed Android installation status not always updated.
  {% endupdate %}

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

## 0.5.2676

* Use autocomplete lists in front-office when list has more than 10 options.
* Fixed compare config.
  {% endupdate %}

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

## 0.5.2661

* Fixed date formatting for profile properties when adding events to Klaviyo.
  {% endupdate %}

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

## 0.5.2653

* Fixed modal not closing when clicking confirm on push update.
* Added “auto” pass provider to bypass pass layout on Apple.
* Added a button to switch environments.
  {% endupdate %}

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

## 0.5.2643

* Fixed back-office logout button when user doesn’t have access to any tenant.
  {% endupdate %}

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

## 0.5.2639

* Fixed barcode API with data containing `/`.
* Fixed bulk store deletion.
* Fixed bad translations in back office.
  {% 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/q2-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.