Coverage remained the same at 100.0% when pulling 9ac0eec2274f01298521b8a43e67672f8ff32c47 on hexo-3 into 5dfc10be777816bd76c1384943fe133bf37da30b on master.
Coverage remained the same at 100.0% when pulling 9ac0eec2274f01298521b8a43e67672f8ff32c47 on hexo-3 into 5dfc10be777816bd76c1384943fe133bf37da30b on master.
Coverage remained the same at 100.0% when pulling 78f7197d2a77125d8cfcb6a5effcb7de716fcbb9 on hexo-3 into 5dfc10be777816bd76c1384943fe133bf37da30b on master.
Coverage remained the same at 100.0% when pulling 78f7197d2a77125d8cfcb6a5effcb7de716fcbb9 on hexo-3 into 5dfc10be777816bd76c1384943fe133bf37da30b on master.
Coverage remained the same at 100.0% when pulling 78f7197d2a77125d8cfcb6a5effcb7de716fcbb9 on hexo-3 into 5dfc10be777816bd76c1384943fe133bf37da30b on master.
Hexo 3 has changed plugin loading mechanism, see https://github.com/hexojs/hexo/wiki/Breaking-Changes-in-Hexo-3.0#plugin-loading-mechanism.
14 might be related but further investigation is definitely in need.
It should be a major version bump as we drops support on
hexo <= 2
, so I put it on 0.4.0 milestone.