Skip to content

Releases: thoughtbot/parity

development

14 Dec 14:58
Compare
Choose a tag to compare
development Pre-release
Pre-release

parity-development.tar.gz
Ongoing development release
Install with:
brew install --devel parity

Be sure to delete your existing cached file if the development version has been updated!

rm ~/Library/Caches/Homebrew/parity-development.tar.gz

v2.2.0

12 May 18:38
Compare
Choose a tag to compare

Fix breaking change in Heroku PG CLI that blocked development restores to Heroku environments.

v2.1.0

24 Mar 16:59
Compare
Choose a tag to compare
  • incorporate changes for easier Linux packaging (thanks @tabfugnic!)
  • fix Heroku CLI argument error related to Heroku change (thanks @pfac!)
  • remove Traveling Ruby packaging

v2.0.1 (only for package managers)

15 Dec 03:01
Compare
Choose a tag to compare

This version has no new functionality relative to version 2.0.0, but has packaging updates to make installation possible again through Homebrew.

v2.0.0

14 Dec 15:04
Compare
Choose a tag to compare
  • Resolve breaking changes from Heroku CLI
  • Add back gem-installed dependencies for users who had trouble installing via package

v1.0.0

16 Sep 15:14
Compare
Choose a tag to compare
  • No more Rubygem-installed executables (install via your package manager)
  • Fast restores from Heroku-remote backups
  • Fancy new major version number

v0.10.0

29 Jul 14:52
Compare
Choose a tag to compare
  • BREAKING CHANGE: remove external gem dependencies that caused problems for some users (5704201)
  • Remove unnecessary packaging code (68eccd7)
  • Use Kernel.exec to allow use of Ctrl-C in long-running processes (e2d965e)
  • Allow restores to production (05ba1f1)
  • Correctly parse HTTPS Git remotes on Heroku (ba07923)

v0.9.3

15 Apr 20:10
Compare
Choose a tag to compare
  • Add restore-from alias.
  • Parse app names with hyphens
  • Update packaging script.

v0.9.2

17 Nov 03:20
Compare
Choose a tag to compare
Version 0.9.2

v0.9.1

11 Nov 23:35
Compare
Choose a tag to compare

Fixes a bug in deploy introduced in v0.9.0.