marked ^12.0.2 → ^13.0.0

[sysmat]

add support for marked 13

[muuvmuuv]

It really feals like marked does major releases every week haha

[sysmat]

Maybe do range in version dependency 27. jun. 2024 20:17 je oseba Marvin Heilemann ***@***.***> napisala: It really feals like marked does major releases every week haha —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#526 (comment)", "url": "#526 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[jfcere]

Marked 13 brings breaking changes and I am following the Angular versioning so I won't update marked until next Angular version.

Due to all the breaking changes, doing range versions is out of the question.

And yeah, marked do update often 😅

[kle-pra]

Marked 14 was just released so probably just try to upgrade to 14 when upgrading with next angular version if possible.

[SEQUOiA87]

Marked 14 was just released so probably just try to upgrade to 14 when upgrading with next angular version if possible.

Did someone already try this and can confirm whether it's working for Marked 14?
Thanks in advance!

[muuvmuuv]

Marked 13 brings breaking changes and I am following the Angular versioning so I won't update marked until next Angular version.

If it breaks something do a major release. That what semver is for. I see no reason to stay on an old peer dep just because of Angular. Create a md-table with which version supports which Angular version. What if marked 13/14/15 has a security fix, do we need to wait for Angular 19/20...? Sry, but I heard that way too often in Angular-Ecosystem