### v0.13.0

#### New features

* Add a `stolonctl` command to force fail a keeper ([sorintlab#546](sorintlab#546))
* Overcome PostgreSQL synchronous replication limitation that could cause lost transactions under some events ([sorintlab#514](sorintlab#514))
* Users can now define `archiveRecoverySettings` in the cluster spec of a standby cluster. One of the possible use cases is to feed the standby cluster only with archived logs without streaming replication. (See Upgrade Notes) ([sorintlab#543](sorintlab#543))
* Keeper: remove trailing new lines from provided passwords ([sorintlab#548](sorintlab#548))

#### Bug Fixes

* Sort keepers addresses in `pg_hba.conf` to avoid unneeded postgres instance reloads ([sorintlab#558](sorintlab#558))
* Set `recovery_target_action` to promote when using recovery target settings [sorintlab#545](sorintlab#545))
* Fixed wrong listen address used in `pg_hba.conf` when `SUReplAccessStrict` mode was enabled ([sorintlab#520](sorintlab#520))

and [many other](https://github.com/sorintlab/stolon/milestone/12) bug fixes and documentation improvements.

Thanks to everybody who contributed to this release.

#### Upgrades notes.

* The clusterspec `standbySettings` option as been replaced by the `standbyConfig` option. Internally it can contain two fields `standbySettings` and `archiveRecoverySettings` (see the clusterspec doc with the descriptors of this new option). If you're updating a standby cluster, BEFORE starting it you should update, using `stolonctl`, the clusterspec with the new `standbyConfig` option.

### v0.12.0

#### New features

* Detect and report when keeper persistent data dir is not the expected one (usually due to wrong configuration, non persistent storage etc...) ([sorintlab#510](sorintlab#510))
* Support PostgresSQL 11 (beta) ([sorintlab#513](sorintlab#513))
* Replication slots declared in the clusterspec `additionalMasterReplicationSlots` option will now be prefixed with the `stolon_` string to let users be able to manually create/drop custom replication slots (See Upgrade Notes) ([sorintlab#531](sorintlab#531))

#### Bug Fixes

* fix wrong address in pg_hba.conf when clusterspec `defaultSUReplAccessMode` is `strict` ([sorintlab#520](sorintlab#520))

and [many other](https://github.com/sorintlab/stolon/milestone/11) bug fixes and documentation improvements.

Thanks to everybody who contributed to this release:

Alexandre Assouad, Lothar Gesslein, @nseyvet

#### Upgrades notes.

* Replication slots declared in the clusterspec `additionalMasterReplicationSlots` option will now be prefixed with the `stolon_` string to let users be able to manually create/drop custom replication slots (they shouldn't start with `stolon_`). Users of these feature should upgrade all the references to these replication slots adding the `stolon_` prefix.

### v0.11.0

#### New features

* In the k8s store backend, stolon components discovery now uses the `component` label instead of the `app` label (See Upgrade Notes) ([sorintlab#469](sorintlab#469))
* Improved docker swarm examples to resemble the k8s one ([sorintlab#482](sorintlab#482))
* If the user enabled ssl/tls use it also for replication/pg_rewind connections ([sorintlab#501](sorintlab#501))
* Remove final newline from example base64 password in k8s example ([sorintlab#505](sorintlab#505))

#### Bug Fixes

* Fixed wrong libkv store election path (See Upgrade Notes) ([sorintlab#479](sorintlab#479))
* Fixed a check in synchronous replication that will block future synchronous standbys updates under some circumstances ([sorintlab#494](sorintlab#494))
* Fixed atomic writes of postgresql genenerated files ([sorintlab#495](sorintlab#495))

Thanks to everybody who contributed to this release:

Bill Helgeson, Niklas Hambüchen, Sylvere Richard, Tyler Kellen

## Upgrades notes.

* In the k8s store backend, the label that defines the kind of stolon component has changed from `app` to `component`. When upgrading you should update the various resource descriptors setting the k8s component name (`stolon-keeper`, `stolon-sentinel`, `stolon-proxy`) inside the `component` label instead of the `app` label.
* When using the etcdv2 store, due to a wrong leader election path introduced in the last release and now fixed, if your sentinel returns an election error like `election loop error {"error": "102: Not a file ...` you should stop all the sentinels and remove the wrong dir using `etcdctl rmdir /stolon/cluster/$STOLONCLUSTER/sentinel-leader` where `$STOLONCLUSTER` should be substituted with the stolon cluster name (remember to set `ETCDCTL_API=2`).

### v0.10.0

#### New features

* Initial support for native kubernetes store ([sorintlab#433](sorintlab#433))
* Improved sync standby management ([sorintlab#444](sorintlab#444))
* Ability to use strict and dynamic hba entries for keeper replication ([sorintlab#412](sorintlab#412))
* Ability to define additional replication slots for external clients ([sorintlab#434](sorintlab#434))
* Improved wal level selection ([sorintlab#450](sorintlab#450))

Thanks to everybody who contributed to this release:

Pierre Alexandre Assouad, Arun Babu Neelicattu, Sergey Kim

### v0.9.0

#### New features

* The logs will be colored only when on a tty or when `--log-color` is provided ([sorintlab#416](sorintlab#416))
* Now the store prefix is configurable `--store-prefix` ([sorintlab#425](sorintlab#425))

#### BugFixes

* Fixed keeper missing waits for instance ready ([sorintlab#418](sorintlab#418))
* Fixed etcdv3 store wrong get leader timeout causing `stolonctl status` errors ([sorintlab#426](sorintlab#426))

Thanks to everybody who contributed to this release:

Pierre Fersing, Dmitry Andreev

### v0.8.0

#### New features

* Added support for etcd v3 api (using --store-backend etcdv3) ([sorintlab#393](sorintlab#393))
* Now the stolon-proxy has tcp keepalive enabled by default and provides options for tuning its behavior ([sorintlab#357](sorintlab#357))
* Added `removekeeper` command to stolonctl ([sorintlab#383](sorintlab#383))
* Added the ability to choose the authentication method for su and replication user (currently one of md5 or trust) ([sorintlab#380](sorintlab#380))

#### BugFixes
* Fixed and improved db startup logic to handle a different pg_ctl start behavior between postgres 9 and 10 ([sorintlab#401](sorintlab#401))
* Fixed keeper datadir locking ([sorintlab#405](sorintlab#405))

and [many other](https://github.com/sorintlab/stolon/milestone/7) bug fixes and documentation improvements.

Thanks to everybody who contributed to this release:

AmberBee, @emdeD, Pierre Fersing

### v0.7.0

#### New features

* Added ability to define custom pg_hba.conf entries ([sorintlab#341](sorintlab#341))
* Added ability to set Locale, Encoding and DataChecksums when initializing a new pg db cluster ([sorintlab#338](sorintlab#338))
* Added stolonctl `clusterdata` command to dump the current clusterdata saved in the store ([sorintlab#318](sorintlab#318))
* Detect if a standby cannot sync due to missing wal files on primary ([sorintlab#312](sorintlab#312))
* Various improvements to proxy logic ([sorintlab#308](sorintlab#308)) ([sorintlab#310](sorintlab#310))
* Added cluster spec option to define additional wal senders ([sorintlab#311](sorintlab#311))
* Added various postgresql recovery target settings for point in time recovery ([sorintlab#303](sorintlab#303))
* Added `--log-level` argument to stolon commands (deprecating `--debug`)  ([sorintlab#298](sorintlab#298))

#### BugFixes
* IPV6 fixes ([sorintlab#326](sorintlab#326))
* Handle null values in pg_file_settings view ([sorintlab#322](sorintlab#322))

and [many other](https://github.com/sorintlab/stolon/milestone/6) bug fixes and documentation improvements

Thanks to everybody who contributed to this release:

Albert Vaca, @emdeD, Niklas Hambüchen, Tim Heckman

v0.6.0

This version introduces various interesting new features (like support for upcoming PostgreSQL 10 and standby cluster) and different bug fixes.

* Support for PostgreSQL 10 ([sorintlab#281](sorintlab#281))
* Standby cluster (for multi site disaster recovery and near zero downtime migration) ([sorintlab#283](sorintlab#283))
* Old dead keeper removal ([sorintlab#280](sorintlab#280))
* On asynchronous clusters elect master only if behind a user defined lag ([sorintlab#268](sorintlab#268))
* Docker standalone, swarm and compose examples ([sorintlab#231](sorintlab#231)) and ([sorintlab#238](sorintlab#238))

* Fix incorrect parsing of `synchronous_standby_names` when using synchronous replication with two or more synchronous standbys ([sorintlab#264](sorintlab#264))
* Fix non atomic writes of local state files ([sorintlab#265](sorintlab#265))

and [many other](https://github.com/sorintlab/stolon/milestone/5)

Thanks to everybody who contributed to this release:

Alexander Ermolaev, Dario Nieuwenhuis, Euan Kemp, Ivan Sim, Jasper Siepkes, Niklas Hambüchen, Sajal Kayan

v0.5.0

This version is a big step forward previous releases and provides many new features and a better cluster management.

* Now the configuration is fully declarative (see [cluster specification](doc/cluster_spec.md) documentation) ([sorintlab#178](sorintlab#178)).
* Ability to create a new cluster starting from a previous backup (point in time recovery) ([sorintlab#183](sorintlab#183))
 * Wal-e backup/restore example ([sorintlab#183](sorintlab#183))
* Better synchronous replication, the user can define a min and a max number of required synchronous standbys and the master will always block waiting for acknowledge by the required sync standbys. Only synchronous standbys will be elected as new master. ([sorintlab#219](sorintlab#219))
* Production ready kubernetes examples (just change the persistent volume provider) ([sorintlab#215](sorintlab#215))
* To keep an unique managed central configuration, the postgresql parameters can now only be managed only using the cluster specification ([sorintlab#181](sorintlab#181))
* When (re)initializing a new cluster (with an empty db, from an existing instance or from a backup) the postgresql parameters are automatically merged in the cluster spec ([sorintlab#181](sorintlab#181))
* Use only store based communication and discovery (removed all the kubernetes specific options) ([sorintlab#195](sorintlab#195))
* Ability to use TLS communication with the store (for both etcd and consul) ([sorintlab#208](sorintlab#208))
* Better standby monitoring and replacement ([sorintlab#218](sorintlab#218))
* Improved logging ([sorintlab#187](sorintlab#187))

Many other [improvements and bug fixes](https://github.com/sorintlab/stolon/milestone/4)

v0.4.0

Some cleanups and changes in preparation for release v0.5.0 that will receive a
big refactor (with different breaking changes) needed to bring a lot of new
features.