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 hexo-renderer-marked to v3.3.0 #68

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 21, 2020

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
hexo-renderer-marked 3.0.0 -> 3.3.0 age adoption passing confidence

Release Notes

hexojs/hexo-renderer-marked

v3.3.0

Compare Source

Feature

  • feat: anchorAlias option to set custom header id [#​172]
    • once enabled, for example in ## [foo](#bar), id will be set as "bar".

Fix

  • fix(postAsset): support post in a subfolder [#​173]
    • a post could be in a subfolder like source/_posts/example/lorem/

v3.2.0

Compare Source

Features

  • feat: mangle option [#​164]
    • a built-in option of marked
    • only useful against a basic crawler used by spam bot.
  • feat: disableNunjucks option [#​166]
    • enable this option to disable processing of Nunjucks tag {{ }} {% %}, particularly useful if you're not going to use tag plugins.
  • feat: extend filter to tokenizer [#​165]
  • feat: 'quotes' option to override smartypants [#​161]
    • it's now possible to specify the quote symbols to replace.
    • e.g. quotes: '«»“”'

Fixes

  • fix: handle invalid URL [#​163]
    • invalid URL like http://localhost:4000lorem is no longer encoded.
  • fix: autolink option should not apply on markdown syntax [#​162]
    • autolink: no longer affects <http://example.com>.
    • on another note, marked renderer doesn't detect example.com, if a link doesn't starts with protocol (e.g. http://), a link must starts with www to be detected (for autolink).

v3.1.0

Compare Source

Features

  • feat: postAsset to prepend post's relative path [#​159]
    • With this feature, asset_img tag plugin is no longer required.
    • Only applies to post_asset_folder
    • An example is "image.jpg" is located at "/2020/01/02/foo/image.jpg", which is a post asset of "/2020/01/02/foo/".
      • ![](image.jpg) becomes <img src="/2020/01/02/foo/image.jpg">
    • To enable:

_config.yml

post_asset_folder: true
marked:
prependRoot: true
postAsset: true


- feat: lazyload [#&#8203;156]
* Load image only when it's coming into view. [Explainer](https://togithub.com/scott-little/lazyload)
* `loading="lazy"` will be injected to every image embed `<img>`.
* Only takes effect on [supported browsers](https://caniuse.com/#feat=loading-lazy-attr).
* To enable:
``` yml
marked:
  lazyload: true

Dependency

  • chore(deps-dev): bump hexo from 4.2.1 to 5.0.0 [#​158]

Configuration

📅 Schedule: 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, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot requested a review from SukkaW August 21, 2020 11:17
@renovate renovate bot force-pushed the renovate/hexo-renderer-marked-3.x branch from ffe39f5 to ea3a29a Compare October 27, 2020 08:49
@renovate renovate bot changed the title fix(deps): update dependency hexo-renderer-marked to v3.1.0 fix(deps): update dependency hexo-renderer-marked to v3.3.0 Oct 27, 2020
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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.

2 participants