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(deps): update dependency rehype-slug to v6 #42

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 18, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
rehype-slug 5.1.0 -> 6.0.0 age adoption passing confidence

Release Notes

rehypejs/rehype-slug (rehype-slug)

v6.0.0

Compare Source

Change
  • 295ac26 Update @types/hast, unified, utilities, etc
    migrate: update too
  • 12f76f8 Change to require Node.js 16
    migrate: update too
  • 6855bcc Change to use exports
    migrate: don’t use private APIs

Full Changelog: rehypejs/rehype-slug@5.1.0...6.0.0


Configuration

📅 Schedule: Branch creation - "* * * * 0,6" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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/rehype-slug-6.x branch 2 times, most recently from 943de47 to 364ccfe Compare June 9, 2024 13:12
@renovate renovate bot force-pushed the renovate/rehype-slug-6.x branch from 364ccfe to fe9d959 Compare October 7, 2024 14:20
@renovate renovate bot force-pushed the renovate/rehype-slug-6.x branch from fe9d959 to 879a05c Compare October 19, 2024 13:41
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.

0 participants