# V0.90 Important Announcement

**URL:** <https://community.nocodb.com/t/v0-90-important-announcement/79>\
**Category:** Announcements\
**Created:** [March 31, 2022, 4:00pm UTC](https://community.nocodb.com/t/v0-90-important-announcement/79 "2022-03-31T16:00:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wingkwong](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.nocodb.com/wingkwong/32/4_2.png) [@wingkwong](https://community.nocodb.com/u/wingkwong)\
**Post date:** [March 31, 2022, 4:00pm UTC](https://community.nocodb.com/t/v0-90-important-announcement/79/1 "2022-03-31T16:00:00Z")

</div>

# IMPORTANT ANNOUNCEMENT

On behalf of NocoDB Team, I would like to announce that we have made a significant number of new features and improvements and will be released as `v0.90` soon. However, some breaking changes are expected from `v0.90` onwards.

UPD: [v0.90 Release Note](https://github.com/nocodb/nocodb/releases/tag/0.90.0)

## Data APIs

### REST APIs

- The URL paths to APIs are changing and the old URL paths **will be deprecated on 30 Jun 2022**.
- The responses to APIs will be changed.
- Swagger UI will be removed and may be supported in the future release.

| Old URL Path (\< v0.90) | New URL Path (v0.90) |
| --- | --- |
| /nc/{projectId}/api/v1/{tableAlias}  
`Deprecated on 30 Jun 22` | /api/v1/db/data/{orgs}/{projectName}/{tableName}   
 /api/v1/db/data/{orgs}/{projectName}/{tableId} |
| /nc/{projectId}/api/v1/{tableAlias}/{rowId}  
`Deprecated on 30 Jun 22` | /api/v1/db/data/{orgs}/{projectName}/{tableName}/{rowId} |

> Currently, the default value for {orgs} is `noco`. Users will be able to change it in the future release.

### GraphQL APIs

GraphQL APIs, unfortunately, will be deprecated form `v0.90` onwards - which means

- Users won’t be able to create a GraphQL project nor use the GraphQL queries.
- For projects created before `v0.90`, we will convert it to REST API projects.
- The rationale behind is that GraphQL is a really small use case of NocoDB users and smart spreadsheet are usually flat representation of data (may be one level nested) which means there will be additional wrangling of json and GQL schema when users are changing the schema dynamically.

## Thank You

We would like to thank all the users and contributors to join the journey with us. If you have any questions, please feel free to post your questions to [Discord](https://discord.gg/5RgZmkW). If you are interested to contribute, please check out [Contribution Guide](https://github.com/nocodb/nocodb/blob/master/.github/CONTRIBUTING.md).