Sha256: 8296883c800a0fcb172a532b412f5e273fc3b604d2012ba2f49f07c15d3f2f37

Contents?: true

Size: 937 Bytes

Versions: 124

Compression:

Stored size: 937 Bytes

Contents

# Upgrading from a previous version of the Pact Broker

## Pact Broker versions >= 2.1.0

Backwards compatibility tests will ensure that the latest version of the database will be compatible with a previous version of the code until v3.0.0 for the following endpoints:

* Tag version
* Publish pact
* Retrieve latest pact
* Retrieve latest pact for tag

This means that zero downtime rolling upgrades for architectures that use multiple web servers (eg. Amazon autoscaling groups) are supported between any two versions from 2.1.0.

When backwards-incompatible changes need to be made in the future, a zero downtime upgrade path will documented on this page.

## Pact Broker < 2.1.0

The upgrades between 1.18.0 and 2.1.0 contains database migrations that are NOT backwards compatible with previous versions of the code. It is recommended to run a single instance of the broker while performing an upgrade that traverses these versions.

Version data entries

124 entries across 124 versions & 1 rubygems

Version Path
pact_broker-2.89.1 UPGRADING.md
pact_broker-2.89.0 UPGRADING.md
pact_broker-2.88.0 UPGRADING.md
pact_broker-2.87.0 UPGRADING.md
pact_broker-2.86.0 UPGRADING.md
pact_broker-2.85.1 UPGRADING.md
pact_broker-2.85.0 UPGRADING.md
pact_broker-2.84.0 UPGRADING.md
pact_broker-2.83.0 UPGRADING.md
pact_broker-2.82.0 UPGRADING.md
pact_broker-2.81.0 UPGRADING.md
pact_broker-2.80.0 UPGRADING.md
pact_broker-2.79.1 UPGRADING.md
pact_broker-2.79.0 UPGRADING.md
pact_broker-2.78.1 UPGRADING.md
pact_broker-2.78.0 UPGRADING.md
pact_broker-2.77.0 UPGRADING.md
pact_broker-2.76.2 UPGRADING.md
pact_broker-2.76.1 UPGRADING.md
pact_broker-2.76.0 UPGRADING.md