`sort` filter should sort sem-ver-wise by default

[salim-b]

I've noticed this is kinda already mentioned as a known issue in the README.

A real-world example where I cannot get the latest version of the Docker image with the existing filters without hardcoding the major version number:

> bump pipeline 'docker:miniflux/miniflux'
1.2.4

> bump pipeline 'docker:miniflux/miniflux|sort|/^\d/'
2.2.9-distroless

# we need to hardcode the major version in the filter to actually get the latest version
> bump pipeline 'docker:miniflux/miniflux|^2'
2.2.15

> bump pipeline 'docker:miniflux/miniflux|^2|/-distroless$/'
2.2.15-distroless

Any chance we could have a sort_semver filter or the like that compares each version number component individually, so it would be fully compatible with semantic versioning?

Masterminds/semver you're importing mentions this. Otherwise there would be the Sort() function from golang.org/x/mod/semver...

[wader]

Masterminds/semver supports wildcard * so you can do:

$ bump pipeline 'docker:miniflux/miniflux|*'
2.2.15

but i'm not sure if that is standard in semver constraints? (any idea if/where that constraint syntax is defined?)

I think i did look into adding some kind of more flexible and liberal version sort thingy in #112 but now i don't remember why i never got finished

[salim-b]

Masterminds/semver supports wildcard * so you can do:

Thanks a lot for the hint! That actually fully covers my needs.

semver: is the default filter if no filter prefix is specified, right? I think this should be documented explicitly and accompanied with a link to the upstream comparator documentation to reduce the chance naive users like me get stuck. 😅

[wader]

👍

Not quite default, it's more that filters can optionally have a "short-form" if they like, for semver that is any string that can be parsed as a constraint. You can see the full-form of the pipeline if you do:

$ bump pipeline -v 'docker:miniflux/miniflux|/hello/|*'
Parsed pipeline: docker:miniflux/miniflux|re:/hello/|semver:*
...

Good point, it's not that well documented. The short/full form is mention here https://github.com/wader/bump?tab=readme-ov-file#configuration but that can probably also be explained a bit more.

[wader]

More semvar docs in #193

[salim-b]

@wader Sorry to bother you again, but I can't manage to get the latest semver release for ghcr.io/formbricks/formbricks:

❯ bump pipeline 'docker:ghcr.io/formbricks/formbricks'
main

❯ bump pipeline 'docker:ghcr.io/formbricks/formbricks|*'
v3.3.0

❯ bump pipeline 'docker:ghcr.io/formbricks/formbricks|sort|/^\d/'
no version found

❯ bump pipeline 'docker:ghcr.io/formbricks/formbricks|sort|/^v\d/'
v3.3.0

❯ bump pipeline 'docker:ghcr.io/formbricks/formbricks|^4'
no version found

Latest release as of today would be 4.4.3...

Let me know if I should open a separate issue for this :)

[wader]

Hey! no worries, i think you probably have run into the same issue as i have also noticed also. I suspect it might be related to docker hub api "pagination", when you get a response with tags it might includes a link header where to continue fetching more tags. It shouldn't be that hard to fix, hope will get to it during the next days.

I wonder if docker hub started doing shorter "pages" and that is why we noticed this now? 🤔

[wader]

Oh this was ghcr.io, but i tried and i do see a link next header in your case also.

[wader]

Try this #198