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.

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

fix(web): update remark (major) #61

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 17, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
remark-gfm 3.0.1 -> 4.0.0 age adoption passing confidence
remark-math (source) 5.1.1 -> 6.0.0 age adoption passing confidence

Release Notes

remarkjs/remark-gfm (remark-gfm)

v4.0.0

Compare Source

Change
  • b8cc334 Update @types/mdast, unified, utilities
    migrate: update too
  • 9eb0f54 Change to use exports
    migrate: don’t use private APIs
  • 5715c93 Change to require Node.js 16
    migrate: update too

Full Changelog: remarkjs/remark-gfm@3.0.1...4.0.0

remarkjs/remark-math (remark-math)

v6.0.0

Compare Source

Change
  • 4223ed9 Change to use exports
    migrate: don’t use private APIs
  • e8039d7 Change to require Node.js 16
    migrate: update too
  • f173346 fc32531 3658edd Change to use <code>, replace wrapping elements, update @types/{hast,mdast}, etc
    migrate: update too
    it’s no longer required to use the syntax extension from remark-math,
    you could instead use fenced code (```math).
    When using remark-math, similar markup is generated (<pre><code class="language-math">).
    To render that nicely (not monospace and small by default), those elements are replaced with
    the results from katex/mathjax.
  • 232f0d7 Remove throwOnError option, improve message
    migrate: check file.messages for warnings
Misc
  • 3aab0e1 Archive remark-html-katex

Full Changelog: remarkjs/remark-math@5.1.1...6.0.0


Configuration

📅 Schedule: Branch creation - "after 10pm every weekend,before 5am every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

Copy link

vercel bot commented Feb 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
reoiam-dev-web ❌ Failed (Inspect) Apr 7, 2024 5:58am

@renovate renovate bot force-pushed the renovate/major-remark branch 2 times, most recently from d69e62f to 12670e8 Compare March 23, 2024 16:20
Copy link
Contributor Author

renovate bot commented Mar 31, 2024

⚠ 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: yarn.lock
error This project's package.json defines "packageManager": "yarn@[email protected]". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants