Skip to content

Conversation

@guanglinn
Copy link
Contributor

@guanglinn guanglinn commented Sep 4, 2024

  1. Update flexmark from 0.42.14 to 0.64.8;
  2. Update some dependency libraries;
  3. Update minSdk from 18 to 21.

@guanglinn
Copy link
Contributor Author

guanglinn commented Sep 4, 2024

Since version 0.42.14, flexmark-java has obtained a large number of improvements and bug fixes, so it is worth upgrading.

Markor works well, and no issues occurred yet after updating flexmark and other libraries.

browser 1.8.0 requires minSdkVersion cannot be smaller than version 19.
appcompat 1.7.0 requires minSdkVersion cannot be smaller than version 21.

Even if we choose API 21 (Android 5.0, in 2014) as minimum SDK, Markor can still run on approximately 99% of devices, so I don't think we need to worry about this.

2024-08-04-min-sdk-version-21

@gsantner
Copy link
Owner

For sure there are improvements at every release. Though is there something specific that gave you reason to get a newer version?

@guanglinn guanglinn marked this pull request as ready for review November 16, 2024 07:43
@guanglinn guanglinn closed this Apr 12, 2025
@gsantner gsantner reopened this Apr 14, 2025
@gsantner gsantner marked this pull request as draft April 14, 2025 08:58
@JSchmerling
Copy link
Contributor

JSchmerling commented Aug 4, 2025

From what I've seen so far, the benefits of upgrading are improved performance (https://github.com/vsch/flexmark-java/wiki/Version-0.60.0-Changes) and better handling of MarkDown extensions (flexmark-all).

@guanglinn guanglinn marked this pull request as ready for review October 23, 2025 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants