Format of releases file name

[wcbing]

Now the tag is 1.1.2-0~ppa1 but the file name is ghostty_1.1.2-0.ppa1_amd64_xxx.deb, ~ was replaces by ..

I make automatic updates for some apt repoes (for Chinese user), and I determine the update and get the file name according to the tag. So, hope the tag and version in file name are the same, thx.

[mkasberg]

Yes, I know what you mean. There are multiple issues at play here but maybe I can do something better. To be clear,

• The GitHub release name is 1.1.2-0~ppa1
• The git tag is actually 1.1.2-0-ppa1 (~ is not allowed in git tag)
• The filename is 1.1.2-0.ppa1, something is changing the ~ to a ..

I think the most obvious fix is to adjust the asset filenames (and figure out what's changing them) so we can have ~ instead of . so it matches the release, as a start. I think I can probably make this change within a week or two.

[wcbing]

• The git tag is actually 1.1.2-0-ppa1 (~ is not allowed in git tag)
• The filename is 1.1.2-0.ppa1, something is changing the ~ to a ..

Oh, I didn't notice that the tag and release name is different. I didn't use the release name.

Then my question is actually the deformation in the git tag and filename is different. Actually, the filename does not have to include ~, just keep it the same as tag.

[wcbing]

I notice the full version in build contains the ~.

After testing, this action will change ~ to ..