Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 20, 2022

This PR contains the following updates:

Package Change Age Confidence
@lekoarts/gatsby-theme-cara (source) 1.2.20 -> 5.1.7 age confidence

Release Notes

LekoArts/gatsby-themes (@​lekoarts/gatsby-theme-cara)

v5.1.7

Compare Source

Patch Changes

v5.1.6

Compare Source

Patch Changes

v5.1.5

Compare Source

Patch Changes

v5.1.4

Compare Source

Patch Changes
  • 409bba45 Thanks @​LekoArts! - Remove link to my Patreon page. To simplify things I disabled my Patreon. If you want to support my OSS work, please consider using GitHub sponsors or Ko-fi. Thanks!

v5.1.3

Compare Source

Patch Changes

v5.1.2

Compare Source

Patch Changes

v5.1.1

Compare Source

Patch Changes
  • #​1164 27abea13 Thanks @​LekoArts! - This theme had a fixed font-size of 18px on the <html> element. This is a bad accessibility practice.
    This explicitly set font-size is removed now.

    This will make the overall font sizes and spacing for the theme smaller (since all other font sizes and padding/margin are derived from the root font-size through rem).

    If you need the old font styles, you can adjust the fontSizes inside the Theme UI configuration.

    Currently, the fontSizes array inside the Theme UI configuration you're using is:

    const fontSizes = [
      "0.875rem",
      "1rem",
      "1.25rem",
      "1.5rem",
      "1.875rem",
      "2.25rem",
      "3rem",
      "4rem",
      "4.5rem",
    ];

    Previously, the font-size was set like this:

    html {
      font-size: 18px;
    }

    So for the normal base of 16px, 18px is 1.125rem. So you could change it to this:

    const fontSizes = [
      "1rem",
      "1.125rem",
      "1.375rem",
      "1.625rem",
      "2rem",
      "2.375rem",
      "3.125rem",
      "4.125rem",
      "4.625rem",
    ];
  • #​1165 b350a5a5 Thanks @​LekoArts! - Ensure that the color mode toggle (light/dark mode) works correctly. This is done through adding the current color mode to the <html> element like so:

    <html class="theme-ui-light"></html>

    When the button is pressed it'll change to:

    <html class="theme-ui-dark"></html>

    In theory this shouldn't be necessary, but there is a weird interaction between Theme UI and Gatsby Head API that I currently don't have the time to deeply investigate.

  • #​1164 27abea13 Thanks @​LekoArts! - Move some global styles from <Global> component to Theme UI's styles.root. This makes it easier to modify those directly through the Theme UI config.

  • #​1134 9298a7de Thanks @​renovate! - fix(deps): update minor and patch dependencies for gatsby-theme-cara

v5.1.0

Compare Source

Minor Changes
  • #​1119 02844608 Thanks @​LekoArts! - Starting with Gatsby 5.3 ESM in Gatsby files is supported now! So you can write gatsby-config.mjs or gatsby-node.mjs.

    Therefore this theme was updated to use ESM for its source code. This shouldn't make a difference for actually using the theme as behavior stays the same. If this is not the case, please open an issue!

    One benefit of now using ESM behind the scenes is that e.g. the remark-* packages could be updated to their latest versions (they are ESM-only). Yey for using up-to-date software.

  • #​1119 02844608 Thanks @​LekoArts! - In the last major version release the siteLanguage key on the siteMetadata object was removed since the Gatsby Head API didn't support setting the lang attribute on the <html> back then. Starting with Gatsby 5.5 this is now supported and the removal change was reverted.

    Thus you can use the siteLanguage key on the siteMetadata object again to change the language globally. By default it uses en. This is also highlighted in the README again. If you want to change the language on a per-page basis, define your own <html lang="value" /> in your Head API export as it then overrides the global configuration.

  • #​1119 02844608 Thanks @​LekoArts! - Because this theme now uses a Gatsby Head API feature that was introduced in Gatsby 5.5 the peerDependencies range was updated from ^5.0.0 to ^5.5.0.

    Please also update your gatsby package when updating this theme.

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes
  • #​1080 296b41a1 Thanks @​LekoArts! - fix: Remove useColorSchemeMediaQuery entry from Theme UI configuration since the "system" setting overwrote the preference of a user. We'd need to wait for Theme UI to implement a proper "system" color mode, see https://redirect.github.com/system-ui/theme-ui/discussions/2264. If you want to have the old behavior, define your own Theme UI configuration as shown in the docs.

  • #​1080 296b41a1 Thanks @​LekoArts! - fix: Improve useColorMode usage by: improving the TS types, adding a SSR fallback to the sun/moon icon toggle so that the correct one is displayed once React is hydrated

  • #​1070 efbc524a Thanks @​renovate! - fix(deps): update minor and patch dependencies for gatsby-theme-cara to ^5.2.0

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes

#​967 ee969f3

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).

v3.0.11

Compare Source

Patch Changes

v3.0.10

Compare Source

Patch Changes

v3.0.9

Compare Source

Patch Changes

v3.0.8

Compare Source

Patch Changes

v3.0.7

Compare Source

Patch Changes

v3.0.6

Compare Source

Patch Changes

v3.0.5

Compare Source

Patch Changes

v3.0.4

Compare Source

Patch Changes

v3.0.3

Compare Source

Patch Changes
  • #​786 32f10a8 Thanks @​renovate! - fix(deps): update minor and patch dependencies (react-spring) for gatsby-theme-cara to ^9.3.2

v3.0.2

Compare Source

Patch Changes

v3.0.1

Compare Source

Patch Changes

v3.0.0

Compare Source

Major Changes

#​641 1598dd6

Compatibility with Gatsby 4. Upgrade your theme to be able to use the new Gatsby release. Leverage Deferred Static Generation (DSG), Server-Side Rendering (SSR) and Parallel Query Running (PQR) with this new release. Learn more about Gatsby 4.

All Gatsby related packages were also upgraded to their latest new major version.

See Gatsby 4 Migration Guide

BREAKING CHANGES:

  • Minimum required Node.js version: >=14.15.0
  • Minimum required gatsby version: ^4.0.0
  • Upgraded Theme UI (packages) from ^0.9.0 to ^0.11.0

Migration:

  • If you used Theme UI in custom components, check the Theme UI changelog
  • Update CI/local environment to account for the new Node.js requirement

v2.0.6

Compare Source

Patch Changes
  • #​696 d0b7944 Thanks @​LekoArts! - chore: Improve READMEs with more instructions

    Links to changelogs and places to ask questions were added.

v2.0.5

Compare Source

Patch Changes

v2.0.4

Patch Changes

v2.0.3

Patch Changes

v2.0.2

Compare Source

Patch Changes

v2.0.1

Compare Source

Patch Changes
  • #​597 e1aec09 Thanks @​renovate! - fix(deps): update packages

    Renovate Bot updates:

    • @react-spring/parallax ^9.1.2 -> ^9.2.3
    • @react-spring/web ^9.1.2 -> ^9.2.3
    • gatsby-plugin-catch-links ^3.6.0 -> ^3.7.0
    • gatsby-plugin-image ^1.6.0 -> ^1.7.0
    • gatsby-plugin-mdx ^2.6.0 -> ^2.7.0
    • gatsby-plugin-react-helmet ^4.6.0 -> ^4.7.0
    • gatsby-plugin-sharp ^3.6.0 -> ^3.7.0
    • gatsby-remark-images ^5.3.0 -> ^5.4.0
    • gatsby-source-filesystem ^3.6.0 -> ^3.7.0
    • gatsby-transformer-sharp ^3.6.0 -> ^3.7.0

v2.0.0

Compare Source

Major Changes

#​599 1785dcf Thanks @​LekoArts!

Breaking Changes
  1. Using lessBabel option for gatsby-plugin-mdx
  2. Updating react-spring from v8 to v9
  3. Updating theme-ui from v0.3 to v0.9 and thus also emotion from v10 to v11
  4. Removed @emotion/styled
  5. Updating all Gatsby related packages to latest
  6. Removed gatsby-plugin-typescript & gatsby-plugin-emotion
Migrating
  1. The lessBabel option might break your setup in some edge cases. If it doesn't work, turn on the mdx option and choose your own config for gatsby-plugin-mdx
  2. You can find the migration guide for react-spring here: https://react-spring.io/changelog#v900. The most notable change is the import that was used inside the components. From import { ParallaxLayer } from "react-spring/renderprops-addons.cjs" to import { ParallaxLayer } from "@&#8203;react-spring/parallax"
  3. The changelog/migration guide for theme-ui is here: https://theme-ui.com/migrating and for emotion here: https://emotion.sh/docs/emotion-11
  4. If you still want to use @emotion/styled you'll need to install it separately now
  5. Gatsby v3 migration guide: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
  6. The TypeScript plugin isn't necessary anymore with Gatsby v3 -- if you want to continue to use @emotion/styled you'll need to add gatsby-plugin-emotion yourself
Improvements
  • You can use the sharp theme option to be able to configure gatsby-plugin-sharp on your own (helpful for defaults for gatsby-plugin-image)
  • Performance improvements from react-spring and theme-ui upgrades
  • Additional props to the ProjectCard component are now spread by default in the components config of gatsby-plugin-theme-ui
Updates to Starter

If you only cloned the starter (https://github.com/LekoArts/gatsby-starter-portfolio-cara) and didn't change anything else this section will be more relevant to you.

  • Conditionally add gatsby-plugin-google-analytics
  • Add FAST_DEV flag
  • Update to all latest Gatsby (+ plugins) versions
  • Add 404 page

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from 389e36d to 50806ee Compare March 17, 2023 12:07
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from 50806ee to ab4d322 Compare May 28, 2023 09:15
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from ab4d322 to ee567f6 Compare June 8, 2023 17:40
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from ee567f6 to ac0062b Compare August 29, 2023 15:56
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from ac0062b to b9d1ffa Compare September 15, 2023 14:02
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from b9d1ffa to c50ca9f Compare December 8, 2023 10:33
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from c50ca9f to d19eec9 Compare February 1, 2024 16:04
@renovate renovate bot changed the title Update dependency @lekoarts/gatsby-theme-cara to v5 Update dependency @lekoarts/gatsby-theme-cara to v5 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/lekoarts-gatsby-theme-cara-5.x branch December 8, 2024 19:01
@renovate renovate bot changed the title Update dependency @lekoarts/gatsby-theme-cara to v5 - autoclosed Update dependency @lekoarts/gatsby-theme-cara to v5 Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from f2e04a6 to d19eec9 Compare December 8, 2024 21:36
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from d19eec9 to 652495a Compare December 24, 2024 12:21
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch 2 times, most recently from 00b00f0 to f8cfb60 Compare August 13, 2025 13:10
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from f8cfb60 to 4aa6e73 Compare August 19, 2025 12:11
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from 4aa6e73 to d55df00 Compare August 31, 2025 12:08
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from d55df00 to 298c288 Compare September 25, 2025 17:50
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from 298c288 to 2c12744 Compare October 21, 2025 18:53
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from 2c12744 to 0bf0906 Compare November 10, 2025 22:51
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from 0bf0906 to 2d2a1bd Compare November 18, 2025 23:35
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-cara-5.x branch from 2d2a1bd to 58b8519 Compare December 3, 2025 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant