versioning mistake when recipe was upgraded to traefik's 3.x branch #57
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
3.3.0+v2.11.26
should've been the last release in the 3.x branch for this recipe, instead the next release was3.4.0+v3.4.4
- which should've been4.0.0+v3.4.4
. But then we just rolled with it. What is the canonical way of fixing versioning mistakes? Should we double-tag the same commits with the correct versions? traefik v3 has introduced breaking changes to the config files so it's pretty important for our versioning to reflect that. paging @ripclap @sixsmith @marlon @p4u1 as active contributorsOh, i thought we found a way to make it backwards compatible for us?
oh, which breaking changes did you run into @knoflook? i saw none on the upgrade...
i understood this was the backwards compat change:
oh ur right this is not a breaking change 🤦 but we should've still bumped our version to follow upstream versioning no? https://docs.coopcloud.tech/maintainers/handbook/#how-are-recipes-versioned
uhm not sure which version you mean specifically? afaict our version follows upstream? https://git.coopcloud.tech/coop-cloud/traefik/tags. there have been releases in the meantime, so things got bumped further.
I mean we're going from traefik 2.x to traefik 3.x and usually that is enough to increase the version number in the co-op cloud recipe but it didn't happen this time
Usually bumping 2.x to 3.x causes backwards incompatible changes but this time it didnt!
See more on reasoning here: #54
Shall we close this?