> For the complete documentation index, see [llms.txt](https://support.rendered.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.rendered.ai/release-notes/rendered.ai-platform/platform-version-0.2.5.md).

# Platform Version 0.2.5

16/Mar/22

**New Features and Improvements**

| Summary                                                                             |
| ----------------------------------------------------------------------------------- |
| Add S3 CORS rule for ana/channel-doc bucket to enable access for UI                 |
| Implement getBankAccounts query on infrastructure & expose it to Platform UI        |
| Change "Instances" to "Peak Instances" on plans page                                |
| Enable Quicksight on production                                                     |
| Trace-ability UI Implementation                                                     |
| Implement backfill script for admin log                                             |
| Release new spot job manager on production                                          |
| Create site for sdk docs.                                                           |
| Update all typography on Platform UI to Text component                              |
| Update AnaRun table to support interpretation info                                  |
| Traceback back-end implementation                                                   |
| Implement sdk and api calls to retrieve channel logs.                               |
| Add Boolean for has created a dataset in the last month to Admin Waitlist reporting |
| Update Stripe API calls to include a try/catch on the stripe client instantiation.  |
| Turn Modal into Custom React Hook                                                   |

**Bug Fixes**

| Summary                                                                      |
| ---------------------------------------------------------------------------- |
| Fix Login Vulnerability                                                      |
| Extra whitespace on the bottom of the billing page/change plan modal         |
| Billing page issue where metadata is returning undefined                     |
| Make graph\_id and staged\_graph\_id optional for setting default graph      |
| Make datasetId required for get\_channel\_runs call                          |
| Change billing plan doesn't work on test environment                         |
| Graph save as button doesn't navigate to new saved graph                     |
| Developer plan showing wrong price in Organizations settings                 |
| Datasets that have valid images should show them in the browse datasets page |
| Graph does not keep node layout locations after Save As                      |
| To find out and fix all unsuccessful api call for Stripe                     |
| Issue with downloading and uploading YAML files.                             |


---

# 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://support.rendered.ai/release-notes/rendered.ai-platform/platform-version-0.2.5.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.