1.0 Release Checklist

I wanted to collect all last-minute tasks we need to accomplish when we publish 1.0. Mostly these changes relate to @chakra-ui/core@latest pointing to 1.0 and https://chakra-ui.com being updated to point to the v1 docs. We’ll need to update various parts of our docs/pipeline to make sure this happens.

• Add Vercel v0.chakra-ui.com alias to existing deployment for chakra-ui.com
• Update alias in vercel.json to https://chakra-ui.com/
• Replace https://chakra-ui.com/ with https://v0.chakra-ui.com/ throughout the project
• Replace https://next.chakra-ui.com/ with https://chakra-ui.com/ throughout the project
• Add link to/note about outdated v0 docs somewhere in the v1 docs (?)
• Replace 1.0.0-next.#-specific versioning with base package names throughout the project (@chakra-ui/core instead of @chakra-ui/core@next)
• Update EDIT_URL to point to master in next.config.js
• Update version/publish scripts to no longer use rc

[ianstormtaylor]

Any updates on the 1.0 release date? Been using 0.8 and there are handful of little bugs throughout the core library. I’ve searched through issues and they’ve been closed because they are fixed in 1.0 (which is great!) but I’m unsure if it’s stable enough to use yet?

FWIW, I’d be personally more interested in a smaller 0.9 that didn’t seek to completely nail the API (I’m fine with breaking changes over time if they are for the better) but fixed a lot of the little annoyances, than to bundle it up into a much larger 1.0 that may take a long time to ship.

[segunadebayo]

I’d suggest we leave the docs as is, and make v1.chakra-ui.com till it’s very stable.