* Package name    : golang-github-yuin-goldmark-highlighting-v2
  Version         : 0.0~git20230729.37449ab-1
  Upstream Author : Yusuke Inuzuka
* URL             : https://github.com/yuin/goldmark-highlighting
* License         : Expat
  Programming Lang: Go
  Description     : A Syntax highlighting extension for the goldmark markdown parser.

This package provides github.com/yuin/goldmark-highlighting/v2

Version 1 is packaged in Debian as golang-github-yuin-goldmark-highlighting

Version 2 is needed for updating Caddy.

v1 is only used by caddy, you can just update it to v2 without
changing source & binary package name when you upload the new version
of caddy.
There is no rule that major versions must be packaged separately. It's
only needed when the transition is hard to coordinate with all the
reverse-depends. (Just comparing to the C libraries, we only add
version suffix in -dev package name when reverse-depends are hard to
adapt to the new api.)

Hi,

Am 18.09.23 um 20:14 schrieb Shengjing Zhu:

Alright :)

Looking at the commits, between the latest commit (37449ab) and the one
in debian (594be19) is close to negligible.

The version of alecthomas/chroma is bumped to v2 and there are some
modifications made in the testing code (highlighting_test.go), that's all.
I'm confused as to why upstream decided to bump * their own version * as well.

Do you think it makes sense to clarify with them on this part?

Also, time being, if you just try to also add another (v2) import path
to yuin-goldmark-highlighting and try to build caddy, does it work? (I'm
guessing it ideally should since there's no change).

Best,
Nilesh