specguard-ruby 0.3.31 → 0.3.32

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 14818808e8ef3b696b1b3834ea590734fa398f5fabbef1c5646d03699e844d99
-  data.tar.gz: ccce2e2cf09f6b3401284c0f7f3f343185c86fa2d48bc43ca7bbd9e48575910e
+  metadata.gz: 4e2f8dd966880d2075d3989184c5f9df89d702445edcdf88583c0b8976021a46
+  data.tar.gz: 4e5d985eda3fb38fc4832412585f6f389a5d9429c915bc9797d02d349576a713
 SHA512:
-  metadata.gz: a7612a5d841ecf6d7b1f675bfe362a5141948c1e227a89d7d90e449c9f3b802b650894e7cd3862bb37a897dcbc77ae6e0d627caa1b3cbde3275b54ebd41beb54
-  data.tar.gz: d78f0bea385d4a9ca63d1581648350c76662f7540b0c105dda6a0ebb15c7b3be1be98e7d2ca8f29b5536fac597a4ed155cb5b96f8ff8575e79bfde7292ff0034
+  metadata.gz: dfc1753a08f2e9c713c61ed12ac18b557f5e32fbaa3577735383ac6adea9bf237ff6374baf6fe276e6735c0e2da38344574c2ab6b02de1a8f42fe41c3fc51aa9
+  data.tar.gz: eca2722d9dcfa6117c21ee589b2b2afdfa422c9983a49d66ee80974574e33f8163f10c2ccab65345badef6dec01d94ad25b436980d5d87beb81b224c3c2c6d1b

data/lib/specguard/client/delivery_warning.rb

@@ -0,0 +1,43 @@
+# frozen_string_literal: true
+
+module SpecGuard
+  module Client
+    # The two clauses that finish a delivery-failure warning line, shared by
+    # the RSpec formatter and the Minitest reporter.
+    #
+    # Both clients print the same sentence after their own prefix and status
+    # clause: where the run ended up, and (when it was saved) the command that
+    # gets it back. They used to carry two inline copies kept equal
+    # "word-for-word" by hand, and the pair had already been co-edited in
+    # separate commits (SPGD-1139, SPGD-1413). One definition here means a
+    # wording change cannot reach one client and miss the other.
+    #
+    # What stays in each client: the prefix, the warning budget (`@warned`),
+    # and the `append` that decides whether `error` is nil. Those differ by
+    # design; only the clause text is shared.
+    module DeliveryWarning
+      module_function
+
+      # Report, not promise. Composed after the write so it can tell the
+      # operator which of the two things actually happened. `error` is the
+      # client's `append` answer: `nil` means the queue took the run (the
+      # success arm, {#replay_clause}); anything else means both sinks are
+      # gone and the run really is lost (SPGD-1413).
+      def sink_clause(path, error)
+        return replay_clause(path) if error.nil?
+
+        "The replay queue #{path} could not be written either " \
+          "(#{error.class}: #{error.message}), so this run's telemetry was lost."
+      end
+
+      # The success arm (SPGD-1139): where the run sits AND the command that
+      # gets it back, fix-the-delivery first and replay after — the order the
+      # ingest CLI's own doctrine describes. The lost-run arm deliberately
+      # names no command: with no queue written there is nothing to replay.
+      def replay_clause(path)
+        "Falling back to #{path}; the test run is unaffected. " \
+          "Once the delivery is fixed, replay this run with: bundle exec specguard-ingest #{path}"
+      end
+    end
+  end
+end

data/lib/specguard/client/ingest_cli.rb

@@ -739,8 +739,7 @@ module SpecGuard
         raise UsageError, "no endpoint is configured (set SPECGUARD_ENDPOINT)" if blank?(configuration.endpoint)
         raise UsageError, "no API key is configured (set SPECGUARD_API_KEY)" if blank?(configuration.api_key)
 
-        transport = Transport.new(endpoint: configuration.endpoint, api_key: configuration.api_key,
-                                  timeout: configuration.timeout, repository_id: configuration.repository_id)
+        transport = Transport.from_configuration(configuration)
         # Asked once, here, so a malformed `SPECGUARD_ENDPOINT` is one exit 2
         # rather than N identical `:failed` lines. `Transport#deliver` would
         # otherwise swallow the same `ArgumentError` once per line and report a

data/lib/specguard/client/transport.rb

@@ -293,6 +293,21 @@ module SpecGuard
         end
       end
 
+      # Builds a transport from a {Configuration}, projecting the four settings
+      # every ingest writer forwards (endpoint, api_key, timeout, repository_id)
+      # so a new keyword is threaded in one place rather than in each writer.
+      #
+      # @param configuration [Configuration, #endpoint, #api_key, #timeout, #repository_id]
+      # @return [Transport]
+      def self.from_configuration(configuration)
+        new(
+          endpoint: configuration.endpoint,
+          api_key: configuration.api_key,
+          timeout: configuration.timeout,
+          repository_id: configuration.repository_id
+        )
+      end
+
       # @param endpoint [String, nil] the installation's base URL. Any trailing
       #   slashes are dropped; a path prefix is preserved, so an installation
       #   behind `https://tools.example.com/specguard` works.

data/lib/specguard/minitest/reporter.rb

@@ -9,6 +9,7 @@ require "fileutils"
 # loads them on a minitest-only consumer's machine.
 require_relative "../client"
 require_relative "../client/configuration"
+require_relative "../client/delivery_warning"
 
 # The annotation lookup is the third framework-free half: what counts as a
 # test's annotation is a property of the source line, not of the framework
@@ -244,12 +245,7 @@ module SpecGuard
 
       def transport_for
         require_relative "../client/transport"
-        SpecGuard::Client::Transport.new(
-          endpoint: @configuration.endpoint,
-          api_key: @configuration.api_key,
-          timeout: @configuration.timeout,
-          repository_id: @configuration.repository_id
-        )
+        SpecGuard::Client::Transport.from_configuration(@configuration)
       end
 
       def row_for(result)
@@ -404,21 +400,10 @@ module SpecGuard
       end
 
       # Report, not promise — see `#fall_back` for why that is the whole of
-      # this slice, and why the order above it did not move.
+      # this slice, and why the order above it did not move. The wording is
+      # shared with the RSpec formatter in {Client::DeliveryWarning}.
       def sink_clause(path, error)
-        return replay_clause(path) if error.nil?
-
-        "The replay queue #{path} could not be written either " \
-          "(#{error.class}: #{error.message}), so this run's telemetry was lost."
-      end
-
-      # The success arm (SPGD-1139): names the configured path (the one
-      # `#append` just wrote) and the replay command, word-for-word the
-      # formatter's clause. The lost-run arm names no command — nothing to
-      # replay.
-      def replay_clause(path)
-        "Falling back to #{path}; the test run is unaffected. " \
-          "Once the delivery is fixed, replay this run with: bundle exec specguard-ingest #{path}"
+        SpecGuard::Client::DeliveryWarning.sink_clause(path, error)
       end
 
       # Once per process, like the formatter's `warn_once`: fifty failing

data/lib/specguard/rspec/formatter.rb

@@ -48,6 +48,7 @@ require "fileutils"
 require_relative "../rspec"
 require_relative "../client/configuration"
 require_relative "../client/transport"
+require_relative "../client/delivery_warning"
 # Brings the linter's discovery chain with it (Scanner, Finding, Schema). That
 # direction is safe — `specguard/rspec` does not require `rspec/core`, so the
 # linter stays loadable without RSpec; it is only the reverse that would break
@@ -1037,12 +1038,7 @@ module SpecGuard
     end
 
     def transport_for(configuration)
-      SpecGuard::Client::Transport.new(
-        endpoint: configuration.endpoint,
-        api_key: configuration.api_key,
-        timeout: configuration.timeout,
-        repository_id: configuration.repository_id
-      )
+      SpecGuard::Client::Transport.from_configuration(configuration)
     end
 
     def blank?(value)
@@ -1201,22 +1197,10 @@ module SpecGuard
 
     # Report, not promise. Composed after the write so it can tell the operator
     # which of the two things actually happened — see {#fall_back} for why that
-    # is the whole of this slice, and why the order above it did not move.
+    # is the whole of this slice, and why the order above it did not move. The
+    # wording is shared with the Minitest reporter in {Client::DeliveryWarning}.
     def sink_clause(path, error)
-      return replay_clause(path) if error.nil?
-
-      "The replay queue #{path} could not be written either " \
-        "(#{error.class}: #{error.message}), so this run's telemetry was lost."
-    end
-
-    # The success arm (SPGD-1139): where the run sits AND the command that gets
-    # it back, fix-the-delivery first and replay after — the order the ingest
-    # CLI's own doctrine describes. The lost-run arm above deliberately names no
-    # command: with no queue written there is nothing to replay. Kept
-    # word-for-word identical to the Minitest reporter's clause.
-    def replay_clause(path)
-      "Falling back to #{path}; the test run is unaffected. " \
-        "Once the delivery is fixed, replay this run with: bundle exec specguard-ingest #{path}"
+      SpecGuard::Client::DeliveryWarning.sink_clause(path, error)
     end
 
     def emit_warning(line)

data/lib/specguard/version.rb

@@ -7,5 +7,5 @@
 # framework-scoped version constant a lie, so the number moved here and the
 # rspec module now points at it for back-compat.
 module SpecGuard
-  VERSION = "0.3.31"
+  VERSION = "0.3.32"
 end

data/script/bump-version.sh

@@ -58,9 +58,9 @@ if git rev-parse -q --verify "refs/tags/v$NEW_VERSION" >/dev/null || \
     exit 1
 fi
 if command -v curl >/dev/null 2>&1; then
-    if curl -fsS --max-time 10 "https://rubygems.org/api/v1/versions/specguard-rspec.json" 2>/dev/null \
+    if curl -fsS --max-time 10 "https://rubygems.org/api/v1/versions/specguard-ruby.json" 2>/dev/null \
        | grep -q "\"number\":\"$NEW_VERSION\""; then
-        echo "Error: specguard-rspec $NEW_VERSION is already published on RubyGems"
+        echo "Error: specguard-ruby $NEW_VERSION is already published on RubyGems"
         exit 1
     fi
 fi

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: specguard-ruby
 version: !ruby/object:Gem::Version
-  version: 0.3.31
+  version: 0.3.32
 platform: ruby
 authors:
 - specguard Agent
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-10-04 00:00:00.000000000 Z
+date: 2026-10-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: json
@@ -52,6 +52,7 @@ files:
 - lib/specguard/client/annotation_scanner.rb
 - lib/specguard/client/cli.rb
 - lib/specguard/client/configuration.rb
+- lib/specguard/client/delivery_warning.rb
 - lib/specguard/client/file_selector.rb
 - lib/specguard/client/finding.rb
 - lib/specguard/client/ingest_cli.rb