An in-range update of marked is breaking the build π¨
greenkeeper opened this issue Β· 1 comments
The dependency marked was updated from 0.6.2
to 0.6.3
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
marked is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
Release Notes for 0.6.3
Fixes
- Fix nested blockquotes #1464
- Fix
<em>
issue with mixed content #1451 - revert #1464 #1497
- Fix
breaks: true
#1507
Docs
- add docs for workers #1432
- Add security policy #1492
- Update supported spec versions #1491
- Update test folder descriptions #1506
DevOps
Commits
The new version differs by 87 commits.
124c576
Release v0.6.3 (#1508)
570af73
0.6.3
1ce85ca
update test descriptions in CONTRIBUTING.md (#1506)
a265632
ποΈ minify [skip ci]
c95667f
Fix breaks (#1507)
e774f77
fix breaks
da4d967
add test
c86d242
update test descriptions in CONTRIBUTING.md
0b7fc5e
ποΈ minify [skip ci]
5ba9ba5
Merge pull request #1497 from UziTech/revert-1464
9c91e40
revert #1464
396591a
Merge pull request #1491 from markedjs/docs-spec-versions
5c6a039
Merge pull request #1492 from markedjs/security-policy
508da4d
add links
9182f80
Add security policy
There are 87 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
After pinning to 0.6.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.