6 Commits

Author	SHA1	Message	Date
Jim Myhrberg	2e2f9bc98a	feat(build): handle macOS Big Sur and later version number	2021-10-10 18:25:38 +01:00
Jim Myhrberg	1bbfe5d3ea	feat(plan): allow build plan to be output as YAML or JSON	2021-10-10 18:25:37 +01:00
Jim Myhrberg	7118ed8560	feat(release): add description to GitHub Releases ... The description includes links to the Emacs source repo used, the git ref, commit, tarball download URL, and build log (GitHub Actions Run).	2021-10-10 18:25:36 +01:00
Jim Myhrberg	fd0ec4d772	fix(plan): correctly parse --test-release-type flag ... The --test-release-type flag was essentially broken and ignored, always creating a prerelease release for test builds. Now it can also produce draft releases.	2021-07-04 23:27:00 +01:00
Jim Myhrberg	f4d6e3a56d	feat(builds): add support for stable builds ... Stable builds are based off of release git tags in Emacs' git repo. Examples of what release tags look like: - emacs-26.1 - emacs-26.2 - emacs-26.3 - emacs-27.1 - emacs-27.2 When the specified git ref looks like a stable release, the plan command will generate a release a different and simpler release name that does not include the date, git sha or ref. Instead, for "emacs-27.2" for example, the emacs-builds release name will be "Emacs-27.2". The "build name", used for naming the disk image, still retains the same format as the nightly builds. Also, non-stable releases are now marked as pre-release on GitHub by default. The reason for the different release name format for stable builds is both to separate them, but also to make it easier to keep the version of the homebrew cask as simply "27.2".	2021-07-03 00:11:59 +01:00
Jim Myhrberg	1ffd735c23	feat(plan): add plan command to create build plans	2021-06-20 18:38:36 +01:00