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

fix(deps): update dependency @lekoarts/gatsby-theme-minimal-blog-core to v6 #255

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update dependency @lekoarts/gatsby-theme-minimal-blog-core to v6 #255

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 6, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@lekoarts/gatsby-theme-minimal-blog-core (source) 4.1.8 -> 6.2.3 age adoption passing confidence

Release Notes

LekoArts/gatsby-themes (@​lekoarts/gatsby-theme-minimal-blog-core)

v6.2.3

Compare Source

Patch Changes

v6.2.2

Compare Source

Patch Changes

v6.2.1

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!

v6.1.3

Compare Source

Patch Changes

v6.1.2

Compare Source

Patch Changes

v6.1.1

Compare Source

Patch Changes

v6.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! - 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.

Patch Changes

v6.0.5

Compare Source

Patch Changes

v6.0.3

Compare Source

Patch Changes

v6.0.0

Compare Source

Major Changes
Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

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

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
Copy link
Contributor Author

renovate bot commented Nov 6, 2023 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"4.25.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^5.5.0" from @lekoarts/[email protected]
npm ERR! node_modules/@lekoarts/gatsby-theme-minimal-blog-core
npm ERR!   @lekoarts/gatsby-theme-minimal-blog-core@"6.2.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-25T11_24_54_240Z-debug-0.log

@netlify Netlify
Copy link

netlify bot commented Nov 6, 2023 •
edited
Loading

❌ Deploy Preview for operate-first-cloud failed.

Name Link
🔨 Latest commit 8fa5f38
🔍 Latest deploy log https://app.netlify.com/sites/operate-first-cloud/deploys/6548aa1cf7fbaf0008e8b5cc

@op1st-prow op1st Prow
Copy link

op1st-prow bot commented Nov 6, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tumido for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@op1st-prow op1st-prow bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 6, 2023
@renovate
fix(deps): update dependency @lekoarts/gatsby-theme-minimal-blog-core…
8fa5f38 
… to v6

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/lekoarts-gatsby-theme-minimal-blog-core-6.x branch from 7f983d9 to 8fa5f38 Compare November 6, 2023 08:55
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jun 4, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"4.25.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^5.5.0" from @lekoarts/[email protected]
npm ERR! node_modules/@lekoarts/gatsby-theme-minimal-blog-core
npm ERR!   @lekoarts/gatsby-theme-minimal-blog-core@"6.2.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-10-09T10_45_12_614Z-debug-0.log

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
size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants