semantic versioning and maintenance of v4

[EinFlex]

Since I have only found limited information about how semantic versioning and maitenance will be handled with the new xberg while the "legacy" tags for kreuzberg are in the same repo I am askig it here.

• Doesn't reseting versions to v1 violate semantic versioning?
• Are the new tags vor xberg icrementally overwriting the previous ones? i.e. will I be able to recover back to a state for v4.6.X once xberg reaches that version? (I don't know git or github behavior that well to know if two tags with the same value can exist)
• Why is xberg even in the same repo as legacy kreuzberg? Wouldn't it be easier for archival and maintenence of legacy systems to seperate the two if resseting to v1 is so important?

I have to maintain systems that won't receive regular updates but still require me to be able to reproduce a certain state in source code in case something fails. Renaming the repo alone already caused issues with our CI and automated testing pipelines. I want to avoid such issues in the future so essentially my question is: Should I prepare to archive used legacy versions of the code now in case the sepcific tags will be overwritten at some point?

Thanks and I appreciate your work!

[Goldziher]

1. we renamed and are publishing under a new name. so It does not.
2. we have the old kreuzberg codebase - its simply on a seperate branch.
3. see 2.

Why are these on the same repo? GH doesnt support moving stars. Its that simple.

[EinFlex]

Thanks. Could you point me to that branch? I can't seem to find it and when looking at legacy tags, Github give me a warning that these tags are not on any branch. Am I missing something here?

[Goldziher]

chore/v4-lts

[Goldziher]

@EinFlex - here: https://github.com/kreuzberg-dev/kreuzberg-lts

This is now the kreuzberg-lts repository. I am publishing v4.10.0 from it at the moment. This is the LTS policy: https://docs.kreuzberg.dev/lts/

Hope this clarifies everything