[ALOY-1739] Alloy: Update releases tags, keep them up to date

GitHub Issuen/a
Resolution Date2020-10-08T09:08:58.000+0000
Affected Version/sn/a
Fix Version/sn/a
ReporterHans Knöchel
AssigneeEwan Harris


As a new developer, coming to the alloy repository can be quite irritating, because the latest release is marked with 2015, although there is still a vivid development around it. Therefore, two things could be done to "Make Alloy releases great again": 1. Mark the latest release (e.g. 1.15.0) as actually latest 2. Include the changelog in the releases page (same for Titanium itself btw - open source developers use that page as their primary source of releases) See a few screenshots attached (Alloy right now vs Vue.js)


Bildschirmfoto 2020-08-30 um 12.58.54.png2020-08-30T11:02:04.000+000027430
Bildschirmfoto 2020-08-30 um 13.02.28.png2020-08-30T11:02:33.000+0000221204


  1. Ewan Harris 2020-09-01 I think this is a fair request for Alloy as we can release an OSS Alloy version a few weeks before it eventually is published via the appc CLI. However, I don't want us creating more work by making this a manual step otherwise it can easily get forgotten about (case in point, I see vue is now at 2.6.12 but the latest is still marked as 2.6.11 ;)). I think we can potentially use semantic-release to achieve automating this, it just means we'll get a little stricter on commit message syntax. I'll leave titanium_mobile as a separate discussion (I can split off to a separate ticket if wanted), personally I think that the releases we do would be too large to list fully on GitHub and that maybe a link to the blog/release notes/changelog would be better suited there
  2. Ewan Harris 2020-10-07 PR: https://github.com/appcelerator/alloy/pull/980 This configures semantic-release on the alloy repo, it will handle the releasing of the package and also tag and create releases for us on GitHub. You can see an example of the releases here https://github.com/appcelerator/titanium-editor-commons/releases
  3. Ewan Harris 2020-10-08 PR merged, from our next release onwards we'll start producing GitHub releases with the associated changelog

JSON Source