> 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.md).

# Release note

Release notes for The Wallet Crew platform, with dated entries listing new features, improvements, fixes and API changes, grouped by quarter.

The Wallet Crew platform ships updates continuously. This page summarises the three most recent releases; the complete history is split into one page per quarter, listed below.

## Latest releases

### 9 October 2026

* Apple Wallet pass templates can carry a management link, pointing end-users to the page where they manage their ticket.

[Full details in Q4 2026](/changelog/release-note/2026/q4-2026.md)

### 8 October 2026

* AI assistants connected through MCP can now create, update and delete passes, pass templates, themes and automations, with a confirmation step before anything changes.
* Apple Wallet passes gain number and date formats, a "place" featured action opening Apple Maps, and a live message on event tickets.
* Passes migrated from another wallet provider keep receiving updates.

[Full details in Q4 2026](/changelog/release-note/2026/q4-2026.md)

### 7 October 2026

* A new automation trigger runs when a chosen pass value changes.
* Stamp cards on Apple Wallet are displayed like loyalty cards.
* Several fixes to automation conditions, translations and passes list date filters.

[Full details in Q4 2026](/changelog/release-note/2026/q4-2026.md)

## All release notes

### 2026

| Quarter                                            | Period              | Releases |
| -------------------------------------------------- | ------------------- | -------- |
| [Q4 2026](/changelog/release-note/2026/q4-2026.md) | October to December | 7        |
| [Q3 2026](/changelog/release-note/2026/q3-2026.md) | July to September   | 19       |
| [Q2 2026](/changelog/release-note/2026/q2-2026.md) | April to June       | 14       |
| [Q1 2026](/changelog/release-note/2026/q1-2026.md) | January to March    | 10       |

### 2025

| Quarter                                            | Period              | Releases |
| -------------------------------------------------- | ------------------- | -------- |
| [Q4 2025](/changelog/release-note/2025/q4-2025.md) | October to December | 22       |
| [Q3 2025](/changelog/release-note/2025/q3-2025.md) | July to September   | 16       |
| [Q2 2025](/changelog/release-note/2025/q2-2025.md) | April to June       | 21       |
| [Q1 2025](/changelog/release-note/2025/q1-2025.md) | January to March    | 8        |

### 2024

| Quarter                                            | Period              | Releases |
| -------------------------------------------------- | ------------------- | -------- |
| [Q4 2024](/changelog/release-note/2024/q4-2024.md) | October to December | 20       |
| [Q3 2024](/changelog/release-note/2024/q3-2024.md) | July to September   | 10       |


---

# 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.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.