README.md in pact_broker-2.3.0 vs README.md in pact_broker-2.4.0
- old
+ new
@@ -19,17 +19,16 @@
Features:
* A RESTful API for publishing and retrieving pacts.
* An embedded HAL browser for navigating the API.
* Autogenerated documentation for each pact.
-* Dynamically generated network diagrams.
-* Displays provider verificaton results.
+* Dynamically generated network diagrams so you can visualise your microservice network.
+* Displays provider verificaton results so you know if you can deploy safely.
+* Provides badges to display pact verification statuses in your READMEs.
* Enables a pact version to be tagged (ie. "prod") so a provider can verify itself against a fixed version of a pact to ensure backwards compatibility.
* Provides webhooks to trigger a provider build when a consumer publishes a change to a pact.
* Tracks changes between Pact versions so you can tell when a consumer has changed its expectations.
* [Docker Pact Broker][docker]
-
-Travis CI Status: [](https://travis-ci.org/pact-foundation/pact_broker)
### How would I use the Pact Broker?
#### Step 1. Consumer CI build
1. The consumer project runs its tests using the [Pact][pact] library to provide a mock service.