Seeing your changes, @Binnette, I notice you are right, and all other release information we added previously is probably wrong. Because now I see @westnordost's release model. As it seems, he holds back new quests or so for a X.y.z release, as in 1.3 the orchard produce quest is e.g. not included. It seems just usual tags are used, but somehow this confuses the git commit history on GitHub, were for each release tag all master commits are shown and also in the commit view any strange tags are added.
As the quests are hold back (e.g. I doubt 0.14 got any new quests…), we cannot rely on the commit/pull request merge date too. But fortunately we have release notes. And that also explains why these release notes looked wrong when checking the commits. So @westnordost, do you always mentioned in your release notes when a new quest is added? And do think, this information was always correct, i.e. you did not accidentally mentioned it on a wrong version?