hexojs / hexo-migrator-wordpress

WordPress migrator for Hexo.
http://hexo.io/docs/migration.html
MIT License
47 stars 30 forks source link

chore(deps): bump turndown from 6.0.0 to 7.1.1 #124

Closed dependabot[bot] closed 3 years ago

dependabot[bot] commented 3 years ago

Bumps turndown from 6.0.0 to 7.1.1.

Release notes

Sourced from turndown's releases.

v7.1.1

  • Upgrade rollup. Fix #387. 9ad4c1b

https://github.com/domchristie/turndown/compare/v7.1.0...v7.1.1

v7.1.0

  • Add mixmark-io update info. 08ea6d6
  • Update deps. c1b11a3
  • Update SECURITY.md ef41a54
  • Update SECURITY.md 2d68b76
  • Create SECURITY.md b30d120
  • Merge pull request #372 from orchitech/npm-prepare 24070bc
  • Fix build when used as git-linked dependency. c11f982
  • Merge pull request #371 from orchitech/fix-inefficient-whitespace-join 46e6ffa
  • Avoid match-at-end regexp bottleneck in replacement to output joining. Fix #370. 0f9129c
  • Merge pull request #319 from orchitech/preformatted-code e7a9351
  • Add support for interpreting <code> as a preformatted inline element and rendering Markdown accordingly. Fix #318. fc0d49f
  • Merge pull request #317 from orchitech/code-span-rule-fix 04e499e
  • Merge pull request #335 from orchitech/fix-browser-modules-export d741a1d
  • Merge pull request #315 from orchitech/flanking-whitespace-improvements dcf2cf6
  • Fix browser modules export. Fixes domchristie/turndown#334. 8d71a2d
  • Follow CommonMark spec more precisely and make the code span rule even more robust for future Turndown development. Fix #316. 68a22b6
  • Respect original whitespace instead of using hardcoded 0x20. Do not merge ASCII and non-ASCII whitespace. Make sure non-ASCII whitespace is moved out of inline elements to prevent generating broken Markdown. Fix #102. Fix #250. 27bdac0

https://github.com/domchristie/turndown/compare/v7.0.1...v7.1.0

v7.0.1

v7.0.0

Same as v7.0.1 but the npm package includes build files that should be ignored. Use v7.0.1

Commits
Maintainer changes

This version was pushed to npm by martincizek, a new releaser for turndown since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
coveralls commented 3 years ago

Coverage Status

Coverage remained the same at 96.392% when pulling bc7dc1b8a03709c2df9962d1eaf7e094f265c9fa on dependabot/npm_and_yarn/turndown-7.1.1 into 6c03b5c827760ff800b4abab7d9f50a49080141f on master.