Post ARorLUNDQE67XZbE4e by omenos@fosstodon.org
 (DIR) More posts by omenos@fosstodon.org
 (DIR) Post #ARorLUNDQE67XZbE4e by omenos@fosstodon.org
       2023-01-20T01:19:48Z
       
       0 likes, 0 repeats
       
       Did @gitea just change what commit the v1.18.2 tag pointed to? I have two email notifications from GitHub, both for 1.18.2 but:° First email points to 1ae2525° Second points to 3c531d3They were three hours apart in my inbox...
       
 (DIR) Post #ARorLV3OtNqFePKupM by omenos@fosstodon.org
       2023-01-20T01:21:25Z
       
       0 likes, 0 repeats
       
       @gitea Inbox chain:
       
 (DIR) Post #ARorLVRrQRPKsGmRxA by gitea@social.gitea.io
       2023-01-20T01:39:56Z
       
       0 likes, 0 repeats
       
       @omenos yup, the first tag was missing a commit, so it was retagged.
       
 (DIR) Post #ARoriiWYyZCK5Z31ZA by gitea@social.gitea.io
       2023-01-20T01:40:40Z
       
       0 likes, 0 repeats
       
       @omenos the first tag was deleted shortly after it was created, but due to CI pipeline the second release wasn’t completed until the time after
       
 (DIR) Post #ARosnKj6yxD1gSgMVs by omenos@fosstodon.org
       2023-01-20T01:56:31Z
       
       0 likes, 0 repeats
       
       @gitea Thanks for the clarification, I assumed there was some hiccup in the automation pipeline.In the future, I might recommend just bumping the version or adding a patch-on-patch (x.y.z-Z) increment rather than the changing the commit the tag points to. Did a double take today and it gave me pause when I saw this earlier.