Backdating a release to the tag date #5447
Replies: 12 comments 3 replies
-
Repeating my comment on the community forum: This is especially useful for when you're importing a repository with tags. After importation, when you create releases here on GitHub - they will be dated to right-now, not to when the tag was created or some appropriate time in the past. |
Beta Was this translation helpful? Give feedback.
-
I'm very interested in this functionality too. Sometimes you just have to correct something and not having the releases on the correct date and in the correct order just makes things confusing. |
Beta Was this translation helpful? Give feedback.
-
Copying an answer from #6646 with minor tweaks. Currently there are at least 2 dates associated with the release, and potentially as many as 3! You have: The date of the commit Here's where things get tricky. By default a tag is not annotated (docs)... this means the tag has no specific meta data associated with it (such as author or date) and is just a loose pointer to a commit. You need to run tag with So here is where it gets fun! Let's say you made a release candidate, and that RC is the exact same commit as your release, but you use non annotated tags. On our end we actually don't know the difference between the two tags aside from the fact that they have different names, and depending on the way you are doing alphabetical sort 1.2.3-rc.1 could sort above 1.2.3... not the outcome you want! So we use the release date of the GitHub release to be the canonical date of the "GitHub release", but it is not meant to be a substitution for the tag or commit. In fact we use the tag / commit date to sort releases rather than the GitHub Release date to ensure we order releases based on their canonical release date, not the date of the GitHub Release That said, if someone made a release candidate and promoted it to be a full release using non annotated tags we could end up with a date that is before the actual release. On to the suggested solution. We could allow for a customized release date, but considering we already have 3 different ways of making the date, and that you can customize the date of the tags itself I don't think it would be a good idea for us to introduce a 4th possible date. We do show the GitHub Release date as the primary date in the feed and on the release itself, which is something that we could explore changing... but for the 99% case the GitHub Release date is likely to be the expected date of the release, and if you think of it like a blog post, the publish day of the post is the "day" of the GitHub release. Anyways... apologies for the many many words to say "it's complicated"... but unfortunately like most times when dealing with computers, dates are hard 🙃 |
Beta Was this translation helpful? Give feedback.
-
I agree with @eyalroz -- there's nothing complicated with adding a combo box when drafting a release to choose whether you are interested in tag's date or current date. |
Beta Was this translation helpful? Give feedback.
-
Confusingly, a draft created from a tag shows the date of the commit, not the date the draft was created -- which makes it seem that will be the date when published. However when changed to published, the date changes to the publish date. |
Beta Was this translation helpful? Give feedback.
-
If you created tags but forgot to create the associated GH releases immediately, then the dates will be messed up. And that's irritating. |
Beta Was this translation helpful? Give feedback.
-
Bumping this as I'm still interested in a solution such as https://github.com/orgs/community/discussions/5447#discussioncomment-1875477 |
Beta Was this translation helpful? Give feedback.
-
Bumping again. Simply being able to edit the release date via the web or releases API would be sufficient for us. |
Beta Was this translation helpful? Give feedback.
-
Was about to create a bunch of releases from a bunch of tags. So yeah, bumping too. |
Beta Was this translation helpful? Give feedback.
-
Obviously, the release date (release publication date) does not always equal to date of release page creation. What is now on github is the date of release page creation, release notes page. For various reasons: when migrating a repository from another hosting, when forgot to create release page, anything happens. We could separate the date of page creation and the date of release itself. As wrote above, we can let the user to select between the current date and the tag date (for an exist tag and tag date != current date). The user can create tag with a desired date to desired commit. We should sort releases by release date, not by page creation date. |
Beta Was this translation helpful? Give feedback.
-
Was about to turn a bunch of draft releases with correct dates into public release. So yeah, bumping too. |
Beta Was this translation helpful? Give feedback.
-
As continue https://github.community/t/backdating-a-release-to-the-tag-date/120161
It would be great to be able to manually set the release date.
Beta Was this translation helpful? Give feedback.
All reactions