⛱ Release v0.4.0

This is an umbrella issue for bugfixes, problems and tasks regarding next Theme UI releases.

I updated the changelog to include current additions to both previous and master (incomplete) branches.

Following list is obviously work in progress and a subject to change. Please feel free to discuss it and share your ideas in this issue.

To-Do

v0.3.2 (released)

• Publish @theme-ui @0.3.2-alpha.10
  • gatsby-theme-ui-blog failed with 403
• Test 0.3.2-alpha manually @hasparus
• Make sure CHANGELOG.md is updated
• Publish v0.3.2 from previous branch with bugfixes and minor improvements
• Get all NPM permissions
• Deploy updated docs from previous branch (This is not super urgent, there are mostly fixes to the docs there, no new content per se)

v0.4.0

• Write a changelog
• Publish 0.4.0-rc.7 with newest changes
• Get permissions to deploy the docs? or deploy to another domain.
• Deploy the docs
• Give more people GitHub and NPM permissions.
• Release final prerelease to test in our apps (0.4.0-rc.13)
• Close “Convert to TypeScript” issue https://github.com/system-ui/theme-ui/issues/668

v0.5.0

• Add support for automatic JSX runtime https://github.com/system-ui/theme-ui/pull/1237
• Set up docs to deploy from master branch on git tag (i.e. on NPM release)

Later

• Type check property values against theme scales #832 #1090
• Set up longer CI tests — run tests in a few bigger open source respositories which use Theme UI. We have a huge API surface, and I’m worried our unit tests don’t cover it fully. This would also be a nice check for unexpected breaking changes.
• Solve React context discrepancy bugs
• Migrate to Preconstruct and Changesets
• Make continous canary releases in GitHub Actions
• Continously deploy “next version” docs to another URL in GitHub Actions

cc @lachlanjc @atanasster @joe-bell @dcastil @nandorojo

[hasparus]

@jordie23, You can use the last 0.4.0-rc version and treat it as stable. It won’t get any breaking changes, maybe some important bugfixes.

• Get permissions to deploy the docs? or deploy to another domain.
• Deploy the docs
• Give more people GitHub and NPM permissions.

We’re not publishing it to NPM, because we can’t deploy the docs to the main docs domain, nor change the fact that we link to it on repository page. Organizational problems are slower to solve than software problems.

[dcastil]

@hasparus What do you think about moving #1237 to a v0.5 release? v0.4 is in RC stage, so no new big features are expected and we could speed up the release by postponing this a little.