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

# May 5th

**Changelog released on 2025-05-05**

Welcome to this release. We added missing search result widget types, fixed RTE spacing between tags, restored search completeness and missing fields after enrichment insights, corrected localized field spacing, restored Enrichment insights on product sidebar, auto-refreshed parent category and fixed business rule migration.

## Bug

1. **Enrichment insights missing on product sidebar:** (SP-1094)
2. **Localized fields are missing spacing:** (SP-1102)
3. **Completeness and Missing Fields are not available in the search after creating a new Enrichment insight:** (SP-1105)
4. **RTE adding spaces between tags:** (SP-1151)
5. **Search result widget missing types:** (SP-1154)
6. **Business rule are not migrated correctly:** (SP-149)
7. **Creating a new category should automatically refresh its parent:** (SP-952)

## Task

1. **Cloudinary tweaks:** (SP-1152)


---

# 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.struct.com/changelog/may-2025/may-5th.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.