Closed fgaz closed 1 year ago
Wonderful, thank you! Presumably it'd make sense to bump the v0.3 tag to include the new .desktop file? Not sure what github will do this with the existing 0.3 release already up... I could always add a 0.3.1 tag+release if simpler. Any thoughts?
Pushing a new tag is best, see https://git-scm.com/docs/git-tag#_on_re_tagging
cool - github seems to have coped OK with the force-pushed retag! But let me know if you spot any oddness :-)
I meant an entirely new tag (0.3.1), while keeping the old one (0.3) as it was. See the git manual section I linked for the rationale.
I think the force push broke my package update.
Changing it again is also not ideal, but it's been like this only for half an hour, so could you change 0.3 back and tag a new 0.3.1 release?
Doh! Totally misread your comment. OK. Old tag restored, new one added!
Thanks!