Change the naming pattern of the 'nightlies' release about podman-desktop

[afbjorklund]

If you use git describe, then you don't have to tag snapshots... Also avoids polluting refs/tags

One issue is that you don't tag on main, so there is nothing on that branch to compare it with.

[benoitf]

@afbjorklund but to do releases on github and publish artifacts AFAIK you still need a tag

https://github.com/orgs/community/discussions/24690

[afbjorklund]

I guess these aren't releases (in the traditional sense, that is).

I used this hack: git tag 1.9 $(git merge-base 1.9.x main)

---

EDIT: So it would be something like

$ git tag 1.9 v1.9.0^
$ git describe --tags v0.0.202404091623-ed2eb47^
1.9-64-ged2eb476dd

I think the go module versions are more similar to yours.

They have next version, the commit date, and the commit

[benoitf]

I'm not sure to follow because we need 'GitHub releases' and we set the prerelease flag so we need tags to publish them

[afbjorklund]

It seems some of the new software (like passt) has dropped versions altogether, and only use dates and commits.

If you want to continue to (ab)use the releases, then I think changing v0.0 to v1.10 sounds like the most simple

[benoitf]

it's more for hosting the binaries
where binaries should be stored if not on GitHub releases ?

[benoitf]

or should we create/use another github project to store/host these nightlies