List view
The marked codebase has been around for a while. Things have changed as we have learned better ways to write JS (and new versions of JS have been released). Therefore, while the 1.x release is primarily to prepare users for 2.x, all the 2.x releases are related to modernizing the marked codebase and architecture (actually removing the features marked for deprecation).
No due date•2/2 issues closed[Major].[Minor].[Patch]: A change to the Minor indicates that **we knowingly broke backward compatibility, usually to better comply with the supported specifications**. A change to the Patch indicates that **we believe backward compatibility was maintained while becoming more compliant with the supported specifications**.
No due date•11/11 issues closedA library whose API is unchanged from years ago, has improved security, and complies with modern and much discussed non-ambiguous specifications. Using version 0.3.16 as a baseline, there will be: **No** API changes (output changes to match specifications do not count as part of the API), **no** new features, and **no** deprecated features. **No** known security issues. **No** known issues processing CommonMark and GitHub Flavored Markdown specifications (without reason). Deprecation strategy and identified features to deprecate. Improved foundation of community standards, project maintenance processes, and tooling (make it easier to keep marked from going stale again).
No due date•4/4 issues closed