> For the complete documentation index, see [llms.txt](https://docs.taskade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskade.com/changelog/changelog-2026/june-2026/june-30-2026.md).

# June 30, 2026

{% hint style="info" %}
**Developer highlights.** This section tracks API, MCP, SDK, automation, and Taskade Genesis platform changes for developers. For the full product changelog see [taskade.com/changelog](https://www.taskade.com/changelog); for release newsletters see [taskade.com/blog/updates](https://www.taskade.com/blog/updates).
{% endhint %}

## What's New:

### Private Per-User Data for Taskade Genesis Apps (Row Scoping)

You can now turn on **Private per-user data** for a published Taskade Genesis app directly from the publish menu — no support ticket needed. Pick the project field that identifies each row's owner, and signed-in app users only see the rows that belong to them; rows created through the app are tagged to the signed-in user automatically. See [Add login and roles](/run-your-business-on-genesis/run-your-business/add-login-and-roles.md).

***

### Hardened OIDC Sign-In for Taskade Genesis Apps

OIDC sign-in for Taskade Genesis apps now rejects the insecure `plain` PKCE method (only **S256** is accepted) and strictly validates that `redirect_uri` matches the app's own origin. Standards-compliant integrations keep working unchanged. See [Genesis Authentication](/community-and-sharing/community-and-sharing/genesis-auth.md).

***

### Static Files via public/ in the App Builder

Taskade Genesis apps can now include a `public/` folder whose contents are passed straight through to the published app — drop in images, fonts, `robots.txt`, or other static assets and reference them by path.

***

## Improvements & Fixes:

* Deleting a custom domain now shows its confirmation dialog correctly above the Settings modal.
* General stability, performance, and connector reliability improvements.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.taskade.com/changelog/changelog-2026/june-2026/june-30-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.