Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Changesets: Version Packages #1010

Merged
merged 2 commits into from
Oct 1, 2022
Merged

Changesets: Version Packages #1010

merged 2 commits into from
Oct 1, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 1, 2022

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@lekoarts/rehype-meta-as-attributes@1.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - Moving this utility from v0.x version range to proper semver range. No changes between 0.0.1 and 1.0.0 were made.

@lekoarts/themes-utils@1.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - Moving this utility from v0.x version range to proper semver range. No changes between 0.0.1 and 1.0.0 were made.

@lekoarts/gatsby-theme-cara@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 in Theme UI config is set to system

    Migration:

    • Internally the necessary changes of the gatsby-plugin-mdx migration guide 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 to be compliant.
    • See Theme UI's migration guide
    • 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. 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).

@lekoarts/gatsby-theme-emilia@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 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 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 to be compliant.
    • See Theme UI's migration guide
    • 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. 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).

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-emilia-core@4.0.0

@lekoarts/gatsby-theme-emilia-core@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 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 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 to be compliant.
    • See Theme UI's migration guide
    • 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. 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).

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/themes-utils@1.0.0

@lekoarts/gatsby-theme-emma@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 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 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 to be compliant.
    • See Theme UI's migration guide
    • 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. 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.

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-emma-core@4.0.0

@lekoarts/gatsby-theme-emma-core@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 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 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 to be compliant.
    • See Theme UI's migration guide
    • 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. 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.

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/themes-utils@1.0.0

@lekoarts/gatsby-theme-graphql-playground@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 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 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 to be compliant.
    • See Theme UI's migration guide
    • 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. 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.

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/themes-utils@1.0.0

@lekoarts/gatsby-theme-jodie@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 in Theme UI config is set to system
    • Removal of body from the Project and Page type. The field contentFilePath was added.
    • Removal of gatsby-omni-font-loader
    • Removal of gatsby-plugin-theme-ui/components and @theme-ui/prism. If you want to have <code> styles, re-add them to your project again (e.g. by using @theme-ui/prism or @mapbox/rehype-prism with gatsby-plugin-mdx)

    Non-Breaking Changes:

    • The homepage images are now served with [AUTO, WEBP, AVIF] (previously it was [AUTO, WEBP])

    Migration:

    • Internally the necessary changes of the gatsby-plugin-mdx migration guide 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 to be compliant.
    • See Theme UI's migration guide
    • 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. 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. The current starter already has this included (you can copy it from there).

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-jodie-core@4.0.0

@lekoarts/gatsby-theme-jodie-core@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 in Theme UI config is set to system
    • Removal of body from the Project and Page type. The field contentFilePath was added.
    • Removal of gatsby-omni-font-loader
    • Removal of gatsby-plugin-theme-ui/components and @theme-ui/prism. If you want to have <code> styles, re-add them to your project again (e.g. by using @theme-ui/prism or @mapbox/rehype-prism with gatsby-plugin-mdx)

    Non-Breaking Changes:

    • The homepage images are now served with [AUTO, WEBP, AVIF] (previously it was [AUTO, WEBP])

    Migration:

    • Internally the necessary changes of the gatsby-plugin-mdx migration guide 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 to be compliant.
    • See Theme UI's migration guide
    • 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. 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. The current starter already has this included (you can copy it from there).

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/themes-utils@1.0.0

@lekoarts/gatsby-theme-minimal-blog@5.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 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 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 to be compliant.

    • See Theme UI's migration guide

    • 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. 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:

      ```js:title=test.js
// content
```

      After:

      ```js title=test.js
// content
```

    • The syntax for adding line highlighting changed.
      Before:

      ```js {1,2-3}
// content
```

      After:

      ```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:

      ```js noLineNumbers
// content that had line numbers by default
```

      After:

      ```js withLineNumbers
// content
```

    • All syntax changes together.
      Before:

      ```js:title=test.js {1,2-3}
// content
```

      After:

      ```js title=test.js highlight=1,2-3 withLineNumbers
// content
```

Patch Changes

  • Updated dependencies [ee969f3, ee969f3]:
    • @lekoarts/gatsby-theme-minimal-blog-core@5.0.0
    • @lekoarts/themes-utils@1.0.0

@lekoarts/gatsby-theme-minimal-blog-core@5.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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 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 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 to be compliant.

    • See Theme UI's migration guide

    • 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. 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:

      ```js:title=test.js
// content
```

      After:

      ```js title=test.js
// content
```

    • The syntax for adding line highlighting changed.
      Before:

      ```js {1,2-3}
// content
```

      After:

      ```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:

      ```js noLineNumbers
// content that had line numbers by default
```

      After:

      ```js withLineNumbers
// content
```

    • All syntax changes together.
      Before:

      ```js:title=test.js {1,2-3}
// content
```

      After:

      ```js title=test.js highlight=1,2-3 withLineNumbers
// content
```

Patch Changes

  • Updated dependencies [ee969f3, ee969f3]:
    • @lekoarts/rehype-meta-as-attributes@1.0.0
    • @lekoarts/themes-utils@1.0.0

@lekoarts/gatsby-theme-specimens@5.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

@lekoarts/gatsby-theme-status-dashboard@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    Breaking Changes:

    • Any breaking changes from theme-ui between v0.11 and v0.15
    • Bump react & react-dom peerDependency to >=18.0.0

    Migration:

@lekoarts/gatsby-theme-styleguide@4.0.0

Major Changes

  • #967 ee969f3 Thanks @LekoArts! - In preparation for the upcoming Gatsby 5 release 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:

    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:

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-specimens@5.0.0

cara@0.2.12

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-cara@4.0.0

emilia@0.3.12

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-emilia@4.0.0

emma@0.3.12

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-emma@4.0.0

graphql-playground@0.2.12

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-graphql-playground@4.0.0

jodie@0.1.6

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-jodie@4.0.0

minimal-blog@1.3.13

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-minimal-blog@5.0.0

specimens@0.3.13

Patch Changes

  • Updated dependencies [ee969f3, ee969f3, ee969f3]:
    • @lekoarts/rehype-meta-as-attributes@1.0.0
    • @lekoarts/themes-utils@1.0.0
    • @lekoarts/gatsby-theme-specimens@5.0.0

status-dashboard@0.2.11

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-status-dashboard@4.0.0

styleguide@0.2.12

Patch Changes

  • Updated dependencies [ee969f3]:
    • @lekoarts/gatsby-theme-styleguide@4.0.0

@gatsby-cloud
Copy link

gatsby-cloud bot commented Oct 1, 2022 •
edited
Loading

✅ cara deploy preview ready

@gatsby-cloud
Copy link

gatsby-cloud bot commented Oct 1, 2022 •
edited
Loading

✅ jodie deploy preview ready

@gatsby-cloud
Copy link

gatsby-cloud bot commented Oct 1, 2022 •
edited
Loading

✅ status-dashboard deploy preview ready

@gatsby-cloud
Copy link

gatsby-cloud bot commented Oct 1, 2022 •
edited
Loading

✅ emilia deploy preview ready

@gatsby-cloud
Copy link

gatsby-cloud bot commented Oct 1, 2022 •
edited
Loading

✅ emma deploy preview ready

@gatsby-cloud
Copy link

gatsby-cloud bot commented Oct 1, 2022 •
edited
Loading

✅ minimal-blog deploy preview ready

@gatsby-cloud
Copy link

gatsby-cloud bot commented Oct 1, 2022 •
edited
Loading

✅ www deploy preview ready

@LekoArts LekoArts merged commit 41a9051 into main Oct 1, 2022
@LekoArts LekoArts deleted the changeset-release/main branch October 1, 2022 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@LekoArts