pact_broker-client 1.29.1 → 1.30.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bc98e7475df1dd176897d28114fcde1ac6799a8bd41219120b7f9de4b26b406c
-  data.tar.gz: 1778f7a4b082b053a16e3b2acb1b128d5b8ca5efa80f80a83ee2dfd543b2f89e
+  metadata.gz: d7be73ef3705005ce0808a1d74dba560c4f590fce09871ae7597c06479ce2316
+  data.tar.gz: ec3b757187ce7c60dbc4835933debbe68fa2f5fb2b08ffdb6f9e5cb7141943e1
 SHA512:
-  metadata.gz: e19b5f513d5c0ca4fc13f814307ad69666518e8813dc6d92e6a7238ff9088a5c53efe9affb2f058111229804d60459f75575bfeb8d2f43f3dc27cf53dd00b6ac
-  data.tar.gz: 1d635d85845756ecdcc96deb0f53d9a7171fc933dd7c184a032e817b6ea02a1448585c3316aaae1b3a2710344fcd3a2a6527bb088ebefb4cd4838ec5b60bcedf
+  metadata.gz: 5f035fa2d68c909fc2d3865ebcd76be24ae9af0a0a4bc4cd0e2503f3a1da822456a6439b61364a83a73ff6e9021a5fa5caa24addeb4f9d9a10980ab33e1ffb74
+  data.tar.gz: 2fe9a489c6c2824f1d218b693559bf1be1713d2989c62283979acc7ddda0684a0b60607fce0abd5d813dbb279c7ff5a4b5ca6bb186c79af3911855803f79837a

data/CHANGELOG.md

@@ -1,3 +1,10 @@
+<a name="v1.30.0"></a>
+### v1.30.0 (2020-10-09)
+
+#### Features
+
+* remove outdated comment from pact publishing output	 ([251b4df](/../../commit/251b4df))
+
 <a name="v1.29.1"></a>
 ### v1.29.1 (2020-08-07)
 

data/Gemfile

@@ -6,10 +6,6 @@ gemspec
 # even thought it's in the development dependencies. Trying it here.
 gem 'rake', '~> 13.0'
 
-group :release do
-  gem 'bump', git: 'https://github.com/bethesque/bump.git'
-end
-
 if ENV['X_PACT_DEVELOPMENT'] == 'true'
   gem 'pact-mock_service', path: '../pact-mock_service'
   gem 'pact-support', path: '../pact-support'

data/README.md

@@ -153,7 +153,7 @@ Can I deploy the latest version of the application Foo that has the tag "test" t
 
 If you are unable to use tags, or there is some other limitation that stops you from using the recommended approach, you can specify one or more of the dependencies explictly. You must also do this if you want to use the `--all TAG` option for any of the pacticipants.
 
-You can specify as many application versions as you like, and you can even specify multiple versions of the same application (repeat the `--pacticipant` name and supply a different version.)
+You can specify as many application versions as you like, and you can even specify multiple versions of the same application (repeat the `--pacticipant` name and supply a different version). If you have a monorepo and you deploy a group of applications together, you can either call `can-i-deploy` once for each application, or you can group them all together by specifying a `--pacticipant` and `--version` for each sub-application.
 
 You can use explictly declared dependencies with or without the `--to ENVIRONMENT`. For example, if you declare two (or more) application versions with no `--to ENVIRONMENT`, then only the applications you specify will be taken into account when determining if it is safe to deploy. If you declare two (or more) application versions _as well as_ a `--to ENVIRONMENT`, then the Pact Broker will work out what integrations your declared applications will have in that environment when determining if it safe to deploy. When using this script for a production release, and you are using tags, it is always the most future-proof option to use the `--to` if possible, as it will catch any newly added consumers or providers.
 
@@ -182,6 +182,13 @@ Can I deploy the latest version of Foo with tag "master" and the latest version
                                --pacticipant Bar --latest master \
                                --broker-base-url BROKER_BASE_URL
 
+Can I deploy all the applications in my monorepo to prod?
+
+    $ pact-broker can-i-deploy --pacticipant A --version a7e28207 \
+                               --pacticipant B --version a7e28207 \
+                               --pacticipant C --version a7e28207 \
+                               --to prod \
+                               --broker-base-url BROKER_BASE_URL                               
 
 Mobile provider use case - can I deploy version b80e7b1b of Bar, all versions of Foo with tag "prod", and the latest version tagged "prod" of any other automatically calculated dependencies together? (Eg. where Bar is a provider and Foo is a mobile consumer with multiple versions in production, and Bar also has its own providers it needs to be compatible with.)
 

data/lib/pact_broker/client/publish_pacts.rb

@@ -95,7 +95,7 @@ module PactBroker
           end
 
           latest_pact_url = pacts.publish(pact_hash: pact, consumer_version: consumer_version)
-          $stdout.puts "The latest version of this pact can be accessed at the following URL (use this to configure the provider verification):\n#{latest_pact_url}"
+          $stdout.puts "The latest version of this pact can be accessed at the following URL:\n#{latest_pact_url}"
           true
         end
       end

data/lib/pact_broker/client/version.rb

@@ -1,5 +1,5 @@
 module PactBroker
   module Client
-    VERSION = '1.29.1'
+    VERSION = '1.30.0'
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pact_broker-client
 version: !ruby/object:Gem::Version
-  version: 1.29.1
+  version: 1.30.0
 platform: ruby
 authors:
 - Beth Skurrie
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-08-07 00:00:00.000000000 Z
+date: 2020-10-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: httparty