v1.0.0

[UziTech]

I think we are ready to release v1.0.0 🎉

This release is meant to be non-breaking for most users so they can get onto a stable release easily.

The only users that will need to change their code are users who are extending the lexer or parser currently. Those users should move to extending the tokenizer and renderer with the new marked.use() function.

After v1.0.0 is released we can look into moving some of the current options into extensions in future releases (as well as making marked more spec compliant). We can maintain some extensions under the @markedjs group but hopefully the community will also follow with some extensions of their own.

Release Notes

Breaking changes

• Add inline tokens to marked.lexer output Inline tokens #1627
• Treat escape token same way as plain text tokens Treat escape token same way we treat plain text tokens #1642
• Add Tokenizer to allow extending token creation Tokenizer #1637

Features

• Add marked.use() method to extend options marked.use #1646

Fixes

• Fix intra-word emphasis can match the wrong asterisks fix: Intra-word emphasis can match the wrong asterisks #1636
• Fix italics modifier (_) breaks links containing underscores fix: Italics modifier (_) breaks links containing underscores #1641
• Fix closing delimited * incorrect for consecutive ocurrences fix: closing delimited * incorrect for consecutive ocurrences #1644

Docs

• Fix lexer data token in demo fix demo table tokens #1638

CI

• Move to GitHub Actions GitHub actions #1635
• Update devDependencies update devdeps #1648

---

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/2i2a4afnt
✅ Preview: https://markedjs-git-fork-uzitech-release-100.markedjs.now.sh

[joshbruce]

I can appreciate this. Feels like something we've heard periodically from users (need a 1.0) while incorporating a lot of the other things we said we wanted to have before doing so - short of spec-compliance. Do eet!

[calculuschild]

[styfle]

[UziTech]