Release 0.8.1

[UziTech]

Release Notes

Fixes

• Fix marked --helpmarked --help #1588
• Fix GFM Example 116 code fences Fix GFM Example 116 #1600
• Send inline html to renderer send inline html to renderer #1602 (fixesRenderer.html() is not invoked if HTML is not preceded by a newline #1601)
• Improve docs example for invoking highlight.js Improve example for invoking highlight.js #1603
• Fix block-level elements breaking tables Fix GFM tables not breaking on block-level structures #1598 (fixesHeading immediately following a table is being rendered in the table element #1467)
• break nptables on block-level structures break nptables on block-level structures #1617

---

Publisher

• $ npm version has been run.
• Release notes in draft GitHub release are up to date
• Release notes include which flavors and versions of Markdown are supported by this release
• Committer checklist is complete.
• Merge PR.
• Publish GitHub release using master with correct version number.
• $ npm publish has been run.
• Create draft GitHub release to prepare next release.

Note: If merges to master occur after submitting this PR and before running $ npm pubish you should be able to

1. pull from upstream/master (git pull upstream master) into the branch holding this version,
2. run $ npm run build to regenerate the min file, and
3. commit and push the updated changes.

Committer

In most cases, this should be someone different than the publisher.

• Version in package.json has been updated (see PUBLISHING.md).
• The marked.min.js has been updated; or,
• release does not change library.
• CI is green (no forced merge required).

[vercel]

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/markedjs/markedjs/6rqwcwe36
✅ Preview: https://markedjs-git-fork-uzitech-release-081.markedjs.now.sh

[styfle]

[UziTech]

This should wait on #1617

[UziTech]

@joshbruce this should be ready to go.

[Scrum]

@joshbruce ping ping ping
@UziTech Why don't you publish it yourself? I can help this project if you need help

[UziTech]

@Scrum we need two approvals from @markedjs members before merging any pull request.

That would be great if you could help out. The best way you could start would be just creating pull requests that fix some issues. The issues with the L1 - broken tag are the most important bugs.

[Scrum]

@UziTech Accepted, try to help.

It would be wise to start fixing after the merge of this PR

[UziTech]

This PR just changes the version. The master branch should be up to date.

[joshbruce]

On it. In a meeting. Cheers, Josh

…

On Mar 18, 2020, at 5:31 AM, Ivan Demidov ***@***.***> wrote: @joshbruce@davisjam ping ping ping — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[joshbruce]

@UziTech, @styfle, and @davisjam - can one of y'all actually publish it? I changed laptops at the beginning of this year and still haven't completely set everything up.

[UziTech]

I'll publish it