aws-sdk-dynamodb 1.102.0 → 1.104.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2fb80de15dbfc03d1a5ac2b521838ee6624c7df0a9ae726093bc61df70b3da81
-  data.tar.gz: 1c70d5c93d676b378e2eefdfb26dd9fd0e62447cde026b1acd4628605f54322d
+  metadata.gz: da62dc3e26b6401ec41108bc0593febec775ab4d0940f31ab492bcd3f1a775a7
+  data.tar.gz: c5112d3d2e3566e3326dac388780bb49e0f66ee1365b68de15089fca30a58c03
 SHA512:
-  metadata.gz: 164708e9866e901e54991e8ea670210cd6826db7e07343ef6b3482268b104d8be0549ff4c0feb1c57af2ff2c13461bbfab27422e549b3b529c3412cded961196
-  data.tar.gz: 868453467d81b12b5c8f0aee64751e416a9519456254d629ce1c7f151b070eebb618cea89f12835aa9599cf10f147ab86533e2a7f5a494e665e5db8c137afad3
+  metadata.gz: 6e8d903816034458dcc474e83aca6c3be45493c5f8a47f3d36c48fce410f9095113f3063f83ddc8dd179bbc85197b89e686c31715a10c717369c72ba31cac02d
+  data.tar.gz: 7bc4c4172dfa12d78bd28321c09fa6a7059fb214ee8362f88de481039884f21817ab79ddf8896de06ce4fdbe14f97623541054b155992381aab7c763b9416f7e

data/CHANGELOG.md

@@ -1,6 +1,16 @@
 Unreleased Changes
 ------------------
 
+1.104.0 (2024-02-20)
+------------------
+
+* Feature - Publishing quick fix for doc only update.
+
+1.103.0 (2024-02-14)
+------------------
+
+* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
+
 1.102.0 (2024-02-02)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.102.0
+1.104.0

data/lib/aws-sdk-dynamodb/client.rb

@@ -7327,11 +7327,11 @@ module Aws::DynamoDB
     #   begins backfilling, you can use `UpdateTable` to perform other
     #   operations.
     #
-    # `UpdateTable` is an asynchronous operation; while it is executing, the
-    # table status changes from `ACTIVE` to `UPDATING`. While it is
-    # `UPDATING`, you cannot issue another `UpdateTable` request. When the
-    # table returns to the `ACTIVE` state, the `UpdateTable` operation is
-    # complete.
+    # `UpdateTable` is an asynchronous operation; while it's executing, the
+    # table status changes from `ACTIVE` to `UPDATING`. While it's
+    # `UPDATING`, you can't issue another `UpdateTable` request on the base
+    # table nor any replicas. When the table returns to the `ACTIVE` state,
+    # the `UpdateTable` operation is complete.
     #
     #
     #
@@ -7924,7 +7924,7 @@ module Aws::DynamoDB
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-dynamodb'
-      context[:gem_version] = '1.102.0'
+      context[:gem_version] = '1.104.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

data/lib/aws-sdk-dynamodb.rb

@@ -54,6 +54,6 @@ require_relative 'aws-sdk-dynamodb/customizations'
 # @!group service
 module Aws::DynamoDB
 
-  GEM_VERSION = '1.102.0'
+  GEM_VERSION = '1.104.0'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-dynamodb
 version: !ruby/object:Gem::Version
-  version: 1.102.0
+  version: 1.104.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-02-02 00:00:00.000000000 Z
+date: 2024-02-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core