Skip to content

Latest commit

 

History

History
30 lines (22 loc) · 1.16 KB

RELEASING.md

File metadata and controls

30 lines (22 loc) · 1.16 KB

Release process

Anything merged into the master branch will be deployed automatically ("continuously") to branch release via Github actions, from where it will be picked up by MELPA.

Tagged releases

When merging a change that updates the version number at the top of prettier.el, a corresponding tag will be created on both the master branch (for diffing sources) and the release branch, which makes the release available as a tagged version.

Changelog

Notable changes used to be documented in Github Releases. As of version 0.9.0 they are now documented in CHANGELOG.md.

Installing PRs

A tarball is generated for every pull request. It can be downloaded by going to the Github pull request page, clicking on "Details" for the topmost check (called something like "build (27.1)"), then on "Artifacts" and finally on "prettier.tar".

Github currently insists on wrapping it in a Zip file so you will have to unzip it first. It can then be installed using M-x package-install-file, perhaps for testing PRs prior to merging.