-
-
Notifications
You must be signed in to change notification settings - Fork 543
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
BREAKING: MDX v2, Theme UI v0.15, Gatsby Head API (#967)
- Loading branch information
Showing
337 changed files
with
9,754 additions
and
10,960 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,104 @@ | ||
| --- | ||
| "@lekoarts/gatsby-theme-minimal-blog": major | ||
| "@lekoarts/gatsby-theme-minimal-blog-core": major | ||
| --- | ||
|
|
||
| In preparation for the upcoming [Gatsby 5 release](https://github.com/gatsbyjs/gatsby/discussions/36609) this release will focus on some breaking changes unrelated to the `gatsby` core package. Another new major version will follow once Gatsby 5 is out so that you can upgrade in steps. | ||
|
|
||
| **Features:** | ||
|
|
||
| - Update to [MDX 2](https://mdxjs.com/blog/v2/) and [`gatsby-plugin-mdx` 4](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/) (**Breaking Change**) | ||
| - Update [Theme UI](https://theme-ui.com/) from v0.11 to v0.15 ([Theme UI Changelog](https://github.com/system-ui/theme-ui/blob/develop/CHANGELOG.md)) (**Breaking Change**) | ||
| - Replace [`react-helmet`](https://github.com/nfl/react-helmet) with [Gatsby Head API](https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-head/) (**Breaking Change**) | ||
| - Improved Typography on the overall site and especially for the blog content | ||
| - Light/Dark Theme for code blocks and overall improved styling for code blocks | ||
|
|
||
| **Breaking Changes:** | ||
|
|
||
| - Any breaking changes from `theme-ui` between v0.11 and v0.15 | ||
| - Bump `react` & `react-dom` peerDependency to `>=18.0.0` | ||
| - Removal of `siteLanguage` from `siteMetadata` | ||
| - The MDX components are not managed by `gatsby-plugin-theme-ui/components` anymore but defined in a `<MDXProvider>` in `src/components/layout` | ||
| - [`useColorSchemeMediaQuery`](https://theme-ui.com/color-modes#responding-to-the-prefers-color-scheme-media-query) in Theme UI config is set to `system` | ||
| - Removal of `body` from the `Post` and `Page` type. The field `contentFilePath` was added. | ||
| - Removal of `gatsby-omni-font-loader` | ||
| - `body` font style is changed from `"IBM Plex Sans"` to a system font stack | ||
| - Removal of `react-live` | ||
| - Change in syntax of highlighting lines, adding code title, and adding line numbers | ||
| - The `showLineNumbers` option is `false` by default now | ||
|
|
||
| **Migration:** | ||
|
|
||
| - Internally the necessary changes of the [gatsby-plugin-mdx migration guide](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#migrating-from-v3-to-v4) were made, but if you set the `mdx` option to `false` and/or shadowed the theme in any way, you'll need to read the migration guide to e.g. change your `gatsby-config`. You'll also need to add any `remarkPlugins` or `rehypePlugins` that the theme is adding by default. | ||
| - MDX 2 is more strict about the allowed syntax, so you'll need to [update your MDX content](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#updating-mdx-content) to be compliant. | ||
| - See [Theme UI's migration guide](https://github.com/system-ui/theme-ui/blob/develop/MIGRATING.md) | ||
| - If you shadowed a file or used `react-helmet` in any form in your site, you'll either need to migrate to the Gatsby Head API or re-install the necessary dependencies. By default, the theme no longer ships with `react-helmet` as internally everything was migrated to Gatsby Head API. To have the `lang` tag work correctly on the `<html>` element you'll need to set it by using the [`setHtmlAttributes` API](https://www.gatsbyjs.com/docs/reference/config-files/gatsby-ssr/#onRenderBody). The current starter already has this included (you can copy it from there). Thus the `<Seo>` component should only be used together with Gatsby Head API. | ||
| - With the removal of `gatsby-omni-font-loader` in the example you'll now need to self-host your fonts and change the Theme UI config. The theme switched to a system font stack in its Theme UI config and the example doesn't provide any custom font anymore. | ||
| - If you want to continue using `react-live`, you have to add the dependency and shadow the `<Code>` component. | ||
| - The syntax for adding code titles changed. | ||
| Before: | ||
|
|
||
| ````md | ||
| ```js:title=test.js | ||
| // content | ||
| ``` | ||
| ```` | ||
|
|
||
| After: | ||
|
|
||
| ````md | ||
| ```js title=test.js | ||
| // content | ||
| ``` | ||
| ```` | ||
|
|
||
| - The syntax for adding line highlighting changed. | ||
| Before: | ||
|
|
||
| ````md | ||
| ```js {1,2-3} | ||
| // content | ||
| ``` | ||
| ```` | ||
|
|
||
| After: | ||
|
|
||
| ````md | ||
| ```js highlight=1,2-3 | ||
| // content | ||
| ``` | ||
| ```` | ||
|
|
||
| - The syntax for adding line numbers changed. You no longer _negate_ line numbers (previously `noLineNumbers`) but opt-in. | ||
| Before: | ||
|
|
||
| ````md | ||
| ```js noLineNumbers | ||
| // content that had line numbers by default | ||
| ``` | ||
| ```` | ||
|
|
||
| After: | ||
|
|
||
| ````md | ||
| ```js withLineNumbers | ||
| // content | ||
| ``` | ||
| ```` | ||
|
|
||
| - All syntax changes together. | ||
| Before: | ||
|
|
||
| ````md | ||
| ```js:title=test.js {1,2-3} | ||
| // content | ||
| ``` | ||
| ```` | ||
|
|
||
| After: | ||
|
|
||
| ````md | ||
| ```js title=test.js highlight=1,2-3 withLineNumbers | ||
| // content | ||
| ``` | ||
| ```` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,30 @@ | ||
| --- | ||
| "@lekoarts/gatsby-theme-emilia": major | ||
| "@lekoarts/gatsby-theme-emilia-core": major | ||
| --- | ||
|
|
||
| In preparation for the upcoming [Gatsby 5 release](https://github.com/gatsbyjs/gatsby/discussions/36609) this release will focus on some breaking changes unrelated to the `gatsby` core package. Another new major version will follow once Gatsby 5 is out so that you can upgrade in steps. | ||
|
|
||
| **Features:** | ||
|
|
||
| - Update to [MDX 2](https://mdxjs.com/blog/v2/) and [`gatsby-plugin-mdx` 4](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/) (**Breaking Change**) | ||
| - Update [Theme UI](https://theme-ui.com/) from v0.11 to v0.15 ([Theme UI Changelog](https://github.com/system-ui/theme-ui/blob/develop/CHANGELOG.md)) (**Breaking Change**) | ||
| - Replace [`react-helmet`](https://github.com/nfl/react-helmet) with [Gatsby Head API](https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-head/) (**Breaking Change**) | ||
| - Improve performance by moving all SVG to [SVG Sprites](https://benadam.me/thoughts/react-svg-sprites/) (**Breaking Change**) | ||
|
|
||
| **Breaking Changes:** | ||
|
|
||
| - Any breaking changes from `theme-ui` between v0.11 and v0.15 | ||
| - Bump `react` & `react-dom` peerDependency to `>=18.0.0` | ||
| - Removal of `siteLanguage` from `siteMetadata` | ||
| - The MDX components are not managed by `gatsby-plugin-theme-ui/components` anymore but defined in a `<MDXProvider>` in `src/components/layout` | ||
| - [`useColorSchemeMediaQuery`](https://theme-ui.com/color-modes#responding-to-the-prefers-color-scheme-media-query) in Theme UI config is set to `system` | ||
| - Removal of `body` from the `Project` type. The field `contentFilePath` was added. | ||
|
|
||
| **Migration:** | ||
|
|
||
| - Internally the necessary changes of the [gatsby-plugin-mdx migration guide](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#migrating-from-v3-to-v4) were made, but if you set the `mdx` option to `false` and/or shadowed the theme in any way, you'll need to read the migration guide to e.g. change your `gatsby-config`. You'll also need to add any `remarkPlugins` or `rehypePlugins` that the theme is adding by default. | ||
| - MDX 2 is more strict about the allowed syntax, so you'll need to [update your MDX content](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#updating-mdx-content) to be compliant. | ||
| - See [Theme UI's migration guide](https://github.com/system-ui/theme-ui/blob/develop/MIGRATING.md) | ||
| - If you shadowed a file or used `react-helmet` in any form in your site, you'll either need to migrate to the Gatsby Head API or re-install the necessary dependencies. By default, the theme no longer ships with `react-helmet` as internally everything was migrated to Gatsby Head API. To have the `lang` tag work correctly on the `<html>` element you'll need to set it by using the [`setHtmlAttributes` API](https://www.gatsbyjs.com/docs/reference/config-files/gatsby-ssr/#onRenderBody). The current starter already has this included (you can copy it from there). Thus the `<Seo>` component should only be used together with Gatsby Head API. | ||
| - The files inside the `assets` folder (`bg-pattern`, `left-arrow`, and `location`) were removed and a new `<Svg>` component was added. The `<Svg>` component is expecting a `icons.svg` file inside the `static` folder. The current starter already has this included (you can copy it from there). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@lekoarts/rehype-meta-as-attributes": major | ||
| --- | ||
|
|
||
| Moving this utility from v0.x version range to proper semver range. No changes between 0.0.1 and 1.0.0 were made. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@lekoarts/themes-utils": major | ||
| --- | ||
|
|
||
| Moving this utility from v0.x version range to proper semver range. No changes between 0.0.1 and 1.0.0 were made. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| --- | ||
| "@lekoarts/gatsby-theme-styleguide": major | ||
| --- | ||
|
|
||
| In preparation for the upcoming [Gatsby 5 release](https://github.com/gatsbyjs/gatsby/discussions/36609) this release will focus on some breaking changes unrelated to the `gatsby` core package. Another new major version will follow once Gatsby 5 is out so that you can upgrade in steps. | ||
|
|
||
| **Features:** | ||
|
|
||
| - Update [Theme UI](https://theme-ui.com/) from v0.11 to v0.15 ([Theme UI Changelog](https://github.com/system-ui/theme-ui/blob/develop/CHANGELOG.md)) (**Breaking Change**) | ||
| - Replace [`react-helmet`](https://github.com/nfl/react-helmet) with [Gatsby Head API](https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-head/) (**Breaking Change**) | ||
| - Support for colors defined in object notation (previously only array notation) | ||
|
|
||
| **Breaking Changes:** | ||
|
|
||
| - Any breaking changes from `theme-ui` between v0.11 and v0.15 | ||
| - Bump `react` & `react-dom` peerDependency to `>=18.0.0` | ||
| - Bump `theme-ui` peerDependency to `>=0.15.0` | ||
| - Add `@emotion/react` as peerDependency | ||
|
|
||
| **Migration:** | ||
|
|
||
| - See [Theme UI's migration guide](https://github.com/system-ui/theme-ui/blob/develop/MIGRATING.md) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| --- | ||
| "@lekoarts/gatsby-theme-cara": major | ||
| --- | ||
|
|
||
| In preparation for the upcoming [Gatsby 5 release](https://github.com/gatsbyjs/gatsby/discussions/36609) this release will focus on some breaking changes unrelated to the `gatsby` core package. Another new major version will follow once Gatsby 5 is out so that you can upgrade in steps. | ||
|
|
||
| **Features:** | ||
|
|
||
| - Update to [MDX 2](https://mdxjs.com/blog/v2/) and [`gatsby-plugin-mdx` 4](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/) (**Breaking Change**) | ||
| - Update [Theme UI](https://theme-ui.com/) from v0.11 to v0.15 ([Theme UI Changelog](https://github.com/system-ui/theme-ui/blob/develop/CHANGELOG.md)) (**Breaking Change**) | ||
| - Replace [`react-helmet`](https://github.com/nfl/react-helmet) with [Gatsby Head API](https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-head/) (**Breaking Change**) | ||
| - Improve performance by moving all SVG to [SVG Sprites](https://benadam.me/thoughts/react-svg-sprites/) (**Breaking Change**) | ||
|
|
||
| **Breaking Changes:** | ||
|
|
||
| - Any breaking changes from `theme-ui` between v0.11 and v0.15 | ||
| - Bump `react` & `react-dom` peerDependency to `>=18.0.0` | ||
| - Removal of `siteLanguage` from `siteMetadata` | ||
| - The MDX components are not managed by `gatsby-plugin-theme-ui/components` anymore but defined in a `<MDXProvider>` in `src/components/layout` | ||
| - [`useColorSchemeMediaQuery`](https://theme-ui.com/color-modes#responding-to-the-prefers-color-scheme-media-query) in Theme UI config is set to `system` | ||
|
|
||
| **Migration:** | ||
|
|
||
| - Internally the necessary changes of the [gatsby-plugin-mdx migration guide](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#migrating-from-v3-to-v4) were made, but if you set the `mdx` option to `false` and/or shadowed the theme in any way, you'll need to read the migration guide to e.g. change your `gatsby-config`. You'll also need to add any `remarkPlugins` or `rehypePlugins` that the theme is adding by default. | ||
| - MDX 2 is more strict about the allowed syntax, so you'll need to [update your MDX content](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#updating-mdx-content) to be compliant. | ||
| - See [Theme UI's migration guide](https://github.com/system-ui/theme-ui/blob/develop/MIGRATING.md) | ||
| - If you shadowed a file or used `react-helmet` in any form in your site, you'll either need to migrate to the Gatsby Head API or re-install the necessary dependencies. By default, the theme no longer ships with `react-helmet` as internally everything was migrated to Gatsby Head API. To have the `lang` tag work correctly on the `<html>` element you'll need to set it by using the [`setHtmlAttributes` API](https://www.gatsbyjs.com/docs/reference/config-files/gatsby-ssr/#onRenderBody). The current starter already has this included (you can copy it from there). Thus the `<Seo>` component should only be used together with Gatsby Head API. | ||
| - The `<Svg>` component is expecting a `icons.svg` file inside the `static` folder. The current starter already has this included (you can copy it from there). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| --- | ||
| "@lekoarts/gatsby-theme-emma": major | ||
| "@lekoarts/gatsby-theme-emma-core": major | ||
| --- | ||
|
|
||
| In preparation for the upcoming [Gatsby 5 release](https://github.com/gatsbyjs/gatsby/discussions/36609) this release will focus on some breaking changes unrelated to the `gatsby` core package. Another new major version will follow once Gatsby 5 is out so that you can upgrade in steps. | ||
|
|
||
| **Features:** | ||
|
|
||
| - Update to [MDX 2](https://mdxjs.com/blog/v2/) and [`gatsby-plugin-mdx` 4](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/) (**Breaking Change**) | ||
| - Update [Theme UI](https://theme-ui.com/) from v0.11 to v0.15 ([Theme UI Changelog](https://github.com/system-ui/theme-ui/blob/develop/CHANGELOG.md)) (**Breaking Change**) | ||
| - Replace [`react-helmet`](https://github.com/nfl/react-helmet) with [Gatsby Head API](https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-head/) (**Breaking Change**) | ||
|
|
||
| **Breaking Changes:** | ||
|
|
||
| - Any breaking changes from `theme-ui` between v0.11 and v0.15 | ||
| - Bump `react` & `react-dom` peerDependency to `>=18.0.0` | ||
| - Removal of `siteLanguage` from `siteMetadata` | ||
| - [`useColorSchemeMediaQuery`](https://theme-ui.com/color-modes#responding-to-the-prefers-color-scheme-media-query) in Theme UI config is set to `system` | ||
| - Removal of `body` from the `Project` and `Page` type. The field `contentFilePath` was added. | ||
|
|
||
| **Migration:** | ||
|
|
||
| - Internally the necessary changes of the [gatsby-plugin-mdx migration guide](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#migrating-from-v3-to-v4) were made, but if you set the `mdx` option to `false` and/or shadowed the theme in any way, you'll need to read the migration guide to e.g. change your `gatsby-config`. You'll also need to add any `remarkPlugins` or `rehypePlugins` that the theme is adding by default. | ||
| - MDX 2 is more strict about the allowed syntax, so you'll need to [update your MDX content](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#updating-mdx-content) to be compliant. | ||
| - See [Theme UI's migration guide](https://github.com/system-ui/theme-ui/blob/develop/MIGRATING.md) | ||
| - If you shadowed a file or used `react-helmet` in any form in your site, you'll either need to migrate to the Gatsby Head API or re-install the necessary dependencies. By default, the theme no longer ships with `react-helmet` as internally everything was migrated to Gatsby Head API. To have the `lang` tag work correctly on the `<html>` element you'll need to set it by using the [`setHtmlAttributes` API](https://www.gatsbyjs.com/docs/reference/config-files/gatsby-ssr/#onRenderBody). The current starter already has this included (you can copy it from there). Thus the `<Seo>` component should only be used together with Gatsby Head API. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| --- | ||
| "@lekoarts/gatsby-theme-graphql-playground": major | ||
| --- | ||
|
|
||
| In preparation for the upcoming [Gatsby 5 release](https://github.com/gatsbyjs/gatsby/discussions/36609) this release will focus on some breaking changes unrelated to the `gatsby` core package. Another new major version will follow once Gatsby 5 is out so that you can upgrade in steps. | ||
|
|
||
| **Features:** | ||
|
|
||
| - Update to [MDX 2](https://mdxjs.com/blog/v2/) and [`gatsby-plugin-mdx` 4](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/) (**Breaking Change**) | ||
| - Update [Theme UI](https://theme-ui.com/) from v0.11 to v0.15 ([Theme UI Changelog](https://github.com/system-ui/theme-ui/blob/develop/CHANGELOG.md)) (**Breaking Change**) | ||
| - Replace [`react-helmet`](https://github.com/nfl/react-helmet) with [Gatsby Head API](https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-head/) (**Breaking Change**) | ||
|
|
||
| **Breaking Changes:** | ||
|
|
||
| - Any breaking changes from `theme-ui` between v0.11 and v0.15 | ||
| - Bump `react` & `react-dom` peerDependency to `>=18.0.0` | ||
| - Removal of `siteLanguage` from `siteMetadata` | ||
| - The MDX components are not managed by `gatsby-plugin-theme-ui/components` anymore but defined in a `<MDXProvider>` in `src/components/layout` | ||
| - [`useColorSchemeMediaQuery`](https://theme-ui.com/color-modes#responding-to-the-prefers-color-scheme-media-query) in Theme UI config is set to `system` | ||
| - Removal of `body` from the `Playground` type. The field `contentFilePath` was added. | ||
| - Changed from `@theme-ui/prism` to `@mapbox/rehype-prism` | ||
|
|
||
| **Migration:** | ||
|
|
||
| - Internally the necessary changes of the [gatsby-plugin-mdx migration guide](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#migrating-from-v3-to-v4) were made, but if you set the `mdx` option to `false` and/or shadowed the theme in any way, you'll need to read the migration guide to e.g. change your `gatsby-config`. You'll also need to add any `remarkPlugins` or `rehypePlugins` that the theme is adding by default. | ||
| - MDX 2 is more strict about the allowed syntax, so you'll need to [update your MDX content](https://www.gatsbyjs.com/plugins/gatsby-plugin-mdx/#updating-mdx-content) to be compliant. | ||
| - See [Theme UI's migration guide](https://github.com/system-ui/theme-ui/blob/develop/MIGRATING.md) | ||
| - If you shadowed a file or used `react-helmet` in any form in your site, you'll either need to migrate to the Gatsby Head API or re-install the necessary dependencies. By default, the theme no longer ships with `react-helmet` as internally everything was migrated to Gatsby Head API. To have the `lang` tag work correctly on the `<html>` element you'll need to set it by using the [`setHtmlAttributes` API](https://www.gatsbyjs.com/docs/reference/config-files/gatsby-ssr/#onRenderBody). The current starter already has this included (you can copy it from there). Thus the `<Seo>` component should only be used together with Gatsby Head API. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| --- | ||
| "@lekoarts/gatsby-theme-status-dashboard": major | ||
| --- | ||
|
|
||
| In preparation for the upcoming [Gatsby 5 release](https://github.com/gatsbyjs/gatsby/discussions/36609) this release will focus on some breaking changes unrelated to the `gatsby` core package. Another new major version will follow once Gatsby 5 is out so that you can upgrade in steps. | ||
|
|
||
| **Features:** | ||
|
|
||
| - Update [Theme UI](https://theme-ui.com/) from v0.11 to v0.15 ([Theme UI Changelog](https://github.com/system-ui/theme-ui/blob/develop/CHANGELOG.md)) (**Breaking Change**) | ||
|
|
||
| **Breaking Changes:** | ||
|
|
||
| - Any breaking changes from `theme-ui` between v0.11 and v0.15 | ||
| - Bump `react` & `react-dom` peerDependency to `>=18.0.0` | ||
|
|
||
| **Migration:** | ||
|
|
||
| - See [Theme UI's migration guide](https://github.com/system-ui/theme-ui/blob/develop/MIGRATING.md) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| --- | ||
| "@lekoarts/gatsby-theme-specimens": major | ||
| --- | ||
|
|
||
| In preparation for the upcoming [Gatsby 5 release](https://github.com/gatsbyjs/gatsby/discussions/36609) this release will focus on some breaking changes unrelated to the `gatsby` core package. Another new major version will follow once Gatsby 5 is out so that you can upgrade in steps. | ||
|
|
||
| **Features:** | ||
|
|
||
| - Support for colors defined in object notation (previously only array notation) | ||
|
|
||
| **Breaking Changes:** | ||
|
|
||
| - Bump `react` & `react-dom` peerDependency to `>=18.0.0` | ||
| - Bump `theme-ui` peerDependency to `>=0.15.0` | ||
|
|
||
| **Migration:** | ||
|
|
||
| - See [Theme UI's migration guide](https://github.com/system-ui/theme-ui/blob/develop/MIGRATING.md) |
Oops, something went wrong.