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

[Snyk] Upgrade @metalsmith/markdown from 1.5.0 to 1.6.0 #5

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

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Sep 3, 2022

Snyk has created this PR to upgrade @metalsmith/markdown from 1.5.0 to 1.6.0.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 3 months ago, on 2022-05-29.
Release notes
Package name: @metalsmith/markdown
  • 1.6.0 - 2022-05-29
    • Resolves #60: support nested keypaths for keys option #60
    • Fixes #61: replace Travis CI badge with GH actions in README.md #61
    • Feature: Add support for simple wildcards, get 100% test coverage 9c53cfe
    • Update supported Node version to >=10, update marked 4.0.12 -> 4.0.16 c0d1a86
  • 1.5.0 - 2022-03-20
    • feat: update marked@2.1.0 to marked@4.0.12 #57
    • feat: Update debug to ^4.3.4 3b6b861
    • feat: export named plugin b9aaa0f
from @metalsmith/markdown GitHub release notes
Commit messages
Package name: @metalsmith/markdown

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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.

SSL cert issues?
1 participant