This new release introduces changes to the administration panel that require a rebuild.
Start by deleting your current build:
```bash
rm -rf ./build
```
Build the administration panel:
```bash
yarn build
# or
npm run build
```
## Updating your code
### Wysiwyg
Wysiwyg was previously an option of the `text` type that was stored in the database. When deploying to production for the first time you had to re-select the option in the interface.
To make sure a Wysiwyg field stays the same when deploying, we introduced the `richtext` type. This type is equivalent to the previous `text` type with `wysiwyg` option enabled.
If you are using [core services](../../3.0.0-beta.x/concepts/services.md), you previously needed to call `result.toJSON()` or `result.toObject()` to get a plain javascript object. This is not the case anymore, you will now receive a simple object directly.
Keep in mind that if you are running custom ORM queries with Bookshelf or Mongoose you will still have to call `toJSON` or `toObject`. Check out this section about [custom queries](../../3.0.0-beta.x/concepts/queries.md#api-reference).
The function exported in `config/functions/bootstrap.js` previously received a callback. This is not the case anymore. You can either use an async function, return a promise or simply run a synchronous function.
If you have custom [hooks](../../3.0.0-beta.x/concepts/hooks.md) in your project, the `initialize` function will not receive a callback anymore. You can either use an async function, return a promise or simply run a synchronous function.