You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
@carlwgeorge I don't know why the tag was not created... I think it was overwritten by a change I made to the repo (I rewrote the history in order to remove very big commits that clogged the history and added 20mb to the repo size; so maybe the tags were not synced correctly before the manipulation).
I just published v53 with the correct tag, is that good enough or would you need a v52 tag too?
78857cf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can a v52 tag be created for this commit to help distro packagers?
78857cf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@carlwgeorge I don't know why the tag was not created... I think it was overwritten by a change I made to the repo (I rewrote the history in order to remove very big commits that clogged the history and added 20mb to the repo size; so maybe the tags were not synced correctly before the manipulation).
I just published v53 with the correct tag, is that good enough or would you need a v52 tag too?
78857cf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can skip straight to v53, that's no problem. Thanks!