increase 1.81.0 → 1.82.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 6f2ef7f235e5b734c84e27a5c949c491ea1faea2c02bcefd84ecd6e8be306a67
4
- data.tar.gz: 9f91afd36c6c932c87a26b30301d8a295e5f3d9aceea8282a8c5c8f3d36d25cf
3
+ metadata.gz: 5003f82376cad0c3a0649ed1049044cc80282c1ffe3fab49f31db26dea176882
4
+ data.tar.gz: e88b81b77401dc95b54f4566e625653291f298a7b75e1e315745b77f83982670
5
5
  SHA512:
6
- metadata.gz: f3b2796ede17705d22a244f5effb99436102d860e4f1484039ee70f2f4cecaf62b7c69e5175acd174060d38a414de2d34c7395a739572e40e6a6bbfc8dc9ff33
7
- data.tar.gz: fd12d3d69da71a1d739733445d3debc69ab90ca97d5ec14832725b85720d9742e8d9a881b48767fda5790713f3e73f258eff67ea44496de91a1d44223489e5f9
6
+ metadata.gz: dcdc47f03e58ce0edb0b8efea31b55a66c7ebdbffaf41e96e8817e78c4b201006ff3376b9a4b4be1b5563dfb43920907cee6beb6ab59a43aaa1bb4e669eed5b9
7
+ data.tar.gz: 3e09f27478c6ea7b33d5fc67ccdd79e76e57b98d0a46a7087363d7bd5c238b48a1258c40af637e68df8716801d8831fb0f666bdc23ce139527478412e825041f
data/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.82.0 (2025-09-19)
4
+
5
+ Full Changelog: [v1.81.0...v1.82.0](https://github.com/Increase/increase-ruby/compare/v1.81.0...v1.82.0)
6
+
7
+ ### Features
8
+
9
+ * **api:** api update ([624dfb0](https://github.com/Increase/increase-ruby/commit/624dfb082089270ae2431cda1b51e544366cf73c))
10
+
3
11
  ## 1.81.0 (2025-09-18)
4
12
 
5
13
  Full Changelog: [v1.80.0...v1.81.0](https://github.com/Increase/increase-ruby/compare/v1.80.0...v1.81.0)
data/README.md CHANGED
@@ -15,7 +15,7 @@ To use this gem, install via Bundler by adding the following to your application
15
15
  <!-- x-release-please-start-version -->
16
16
 
17
17
  ```ruby
18
- gem "increase", "~> 1.81.0"
18
+ gem "increase", "~> 1.82.0"
19
19
  ```
20
20
 
21
21
  <!-- x-release-please-end -->
@@ -187,15 +187,10 @@ module Increase
187
187
  # @!attribute cardholder_address_verification_result
188
188
  # Your decisions on whether or not each provided address component is a match.
189
189
  # Your response here is evaluated against the customer's provided `postal_code`
190
- # and `line1`, and an appropriate network response is generated. For example, if
191
- # you would like to approve all transactions for a given card, you can submit
192
- # `match` for both `postal_code` and `line1` and Increase will generate an
193
- # approval with an Address Verification System (AVS) code that will match all of
194
- # the available address information, or will report that no check was performed if
195
- # no address information is available. If you do not provide a response, the
196
- # address verification result will be calculated by Increase using the available
197
- # address information available on the card. If none is available, Increase will
198
- # report that no check was performed.
190
+ # and `line1`, and an appropriate network response is generated. For more
191
+ # information, see our
192
+ # [Address Verification System Codes and Overrides](https://increase.com/documentation/address-verification-system-codes-and-overrides)
193
+ # guide.
199
194
  #
200
195
  # @return [Increase::Models::RealTimeDecisionActionParams::CardAuthorization::Approval::CardholderAddressVerificationResult, nil]
201
196
  optional :cardholder_address_verification_result,
@@ -232,15 +227,10 @@ module Increase
232
227
  # @!method initialize(line1:, postal_code:)
233
228
  # Your decisions on whether or not each provided address component is a match.
234
229
  # Your response here is evaluated against the customer's provided `postal_code`
235
- # and `line1`, and an appropriate network response is generated. For example, if
236
- # you would like to approve all transactions for a given card, you can submit
237
- # `match` for both `postal_code` and `line1` and Increase will generate an
238
- # approval with an Address Verification System (AVS) code that will match all of
239
- # the available address information, or will report that no check was performed if
240
- # no address information is available. If you do not provide a response, the
241
- # address verification result will be calculated by Increase using the available
242
- # address information available on the card. If none is available, Increase will
243
- # report that no check was performed.
230
+ # and `line1`, and an appropriate network response is generated. For more
231
+ # information, see our
232
+ # [Address Verification System Codes and Overrides](https://increase.com/documentation/address-verification-system-codes-and-overrides)
233
+ # guide.
244
234
  #
245
235
  # @param line1 [Symbol, Increase::Models::RealTimeDecisionActionParams::CardAuthorization::Approval::CardholderAddressVerificationResult::Line1] Your decision on the address line of the provided address.
246
236
  #
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Increase
4
- VERSION = "1.81.0"
4
+ VERSION = "1.82.0"
5
5
  end
@@ -477,15 +477,10 @@ module Increase
477
477
 
478
478
  # Your decisions on whether or not each provided address component is a match.
479
479
  # Your response here is evaluated against the customer's provided `postal_code`
480
- # and `line1`, and an appropriate network response is generated. For example, if
481
- # you would like to approve all transactions for a given card, you can submit
482
- # `match` for both `postal_code` and `line1` and Increase will generate an
483
- # approval with an Address Verification System (AVS) code that will match all of
484
- # the available address information, or will report that no check was performed if
485
- # no address information is available. If you do not provide a response, the
486
- # address verification result will be calculated by Increase using the available
487
- # address information available on the card. If none is available, Increase will
488
- # report that no check was performed.
480
+ # and `line1`, and an appropriate network response is generated. For more
481
+ # information, see our
482
+ # [Address Verification System Codes and Overrides](https://increase.com/documentation/address-verification-system-codes-and-overrides)
483
+ # guide.
489
484
  sig do
490
485
  returns(
491
486
  T.nilable(
@@ -516,15 +511,10 @@ module Increase
516
511
  def self.new(
517
512
  # Your decisions on whether or not each provided address component is a match.
518
513
  # Your response here is evaluated against the customer's provided `postal_code`
519
- # and `line1`, and an appropriate network response is generated. For example, if
520
- # you would like to approve all transactions for a given card, you can submit
521
- # `match` for both `postal_code` and `line1` and Increase will generate an
522
- # approval with an Address Verification System (AVS) code that will match all of
523
- # the available address information, or will report that no check was performed if
524
- # no address information is available. If you do not provide a response, the
525
- # address verification result will be calculated by Increase using the available
526
- # address information available on the card. If none is available, Increase will
527
- # report that no check was performed.
514
+ # and `line1`, and an appropriate network response is generated. For more
515
+ # information, see our
516
+ # [Address Verification System Codes and Overrides](https://increase.com/documentation/address-verification-system-codes-and-overrides)
517
+ # guide.
528
518
  cardholder_address_verification_result: nil
529
519
  )
530
520
  end
@@ -567,15 +557,10 @@ module Increase
567
557
 
568
558
  # Your decisions on whether or not each provided address component is a match.
569
559
  # Your response here is evaluated against the customer's provided `postal_code`
570
- # and `line1`, and an appropriate network response is generated. For example, if
571
- # you would like to approve all transactions for a given card, you can submit
572
- # `match` for both `postal_code` and `line1` and Increase will generate an
573
- # approval with an Address Verification System (AVS) code that will match all of
574
- # the available address information, or will report that no check was performed if
575
- # no address information is available. If you do not provide a response, the
576
- # address verification result will be calculated by Increase using the available
577
- # address information available on the card. If none is available, Increase will
578
- # report that no check was performed.
560
+ # and `line1`, and an appropriate network response is generated. For more
561
+ # information, see our
562
+ # [Address Verification System Codes and Overrides](https://increase.com/documentation/address-verification-system-codes-and-overrides)
563
+ # guide.
579
564
  sig do
580
565
  params(
581
566
  line1:
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: increase
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.81.0
4
+ version: 1.82.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Increase
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2025-09-18 00:00:00.000000000 Z
11
+ date: 2025-09-19 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: connection_pool