> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/release-notes/limio-commerce-release-notes/legacy-releases/limio-release-notes-release-620.md).

# Limio Release Notes - Release 62.0

### New Features and Improvements

**Group categories for new subscription types**

You can now add group categories for new subscriptions types.

The Label of the group\_\_limio item will be used as the display text on the components.

**Prop in checkout page to support rich field text with parsed fields**

Rich text fields will support parsing initial charge & the recurring charge on checkout component.

**Width of label drop-down increased.**

We have have increased the width of the dropdown for offer labels to support labels with longer lengths.

You can now see the entire label name when you select the offer label drop-down in offersV2.

*Screenshot: Increased width for Label name dropdown.*

### Bug Fixes

**Publish/ Rebuild Buttons**

There was a bug where Publish and rebuild button weren't showing the actions correctly which is now fixed in this Release.


---

# 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.limio.com/release-notes/limio-commerce-release-notes/legacy-releases/limio-release-notes-release-620.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.