chrono_forge 0.9.0 → 0.9.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1d7b16cc9e00eb7cc95b21a13331c9bc2dffdfcbd4f4e060c03e876f261fa73c
-  data.tar.gz: 4f9b0b28f7f69f518898ffc1e591087096ac71d84547d4c185c07cc6f0a11643
+  metadata.gz: 482a39dce49e0e88ddc0f7341b2806c7893376863caa658eccdd6111c12a4d62
+  data.tar.gz: aab4017a4b0f90ff68779a0b21b660e34a10ba53a28325f7bcbb801251796ebb
 SHA512:
-  metadata.gz: 208180ae5d6fbe4b3ad30b05f1a60eb231f9bd3135304211ff7861f50e546eb32815ab5e8307e9c910cd1c5a7bdf951777635304ed7c629a7a62f8740df21c85
-  data.tar.gz: e3fac31dc46d1b126e8de982b02fe70d37ac7ffd6233ec643f20f93296237029640e67bb004cfaf7e71d5f60429cbc4702d4efe40951c48915e3bc08e561ec51
+  metadata.gz: 1c1a271dccf9c204633846bc81126b327efb1c176b90181c0dece715f99471a021054f8a892f1a223b11655ededeadc720d34a1a67b7e8ca7cf47a6f9749c175
+  data.tar.gz: 72745635bb4e34011c3ed735dfa3d648e88362824463b34bd719b32727c7d36602d130044861b882abb9685633231a57ce9a223771f08855a9938b1811db8405

data/CHANGELOG.md

@@ -1,5 +1,12 @@
 ## [Unreleased]
 
+## [0.9.1] - 2026-06-25
+
+### Fixed
+
+- `LockStrategy.acquire_lock` no longer raises a `NameError` (`undefined local variable or method 'key'`) on lock contention. The concurrent-execution branch referenced an undefined `key` while building its error message, so the intended, benign `ConcurrentExecutionError` ("currently being executed by job X") was masked by a hard `NameError` on every duplicate/racing execution of the same workflow. It now surfaces the real `ConcurrentExecutionError`.
+- Corrected `#{self.class}` → `#{name}` in `LockStrategy`'s lock log/error messages. These are singleton methods (`class << self`), so `self` is already the class and `self.class` rendered the literal string `Class`; messages now name the strategy class.
+
 ## [0.9.0] - 2026-06-03
 
 ### Added

data/lib/chrono_forge/executor/lock_strategy.rb

@@ -16,7 +16,7 @@ module ChronoForge
             # Check for active execution
             if workflow.locked_at && workflow.locked_at > max_duration.ago
               raise ConcurrentExecutionError,
-                "ChronoForge:#{self.class}(#{key}) job(#{job_id}) failed to acquire lock. " \
+                "ChronoForge:#{name}(#{workflow.key}) job(#{job_id}) failed to acquire lock. " \
                 "Currently being executed by job(#{workflow.locked_by})"
             end
 
@@ -27,7 +27,7 @@ module ChronoForge
               state: :running
             )
 
-            Rails.logger.debug { "ChronoForge:#{self.class}(#{workflow.key}) job(#{job_id}) acquired lock." }
+            Rails.logger.debug { "ChronoForge:#{name}(#{workflow.key}) job(#{job_id}) acquired lock." }
 
             workflow
           end
@@ -43,7 +43,7 @@ module ChronoForge
 
           if !force && current_locked_by != job_id
             raise LongRunningConcurrentExecutionError,
-              "ChronoForge:#{self.class}(#{workflow.key}) job(#{job_id}) executed longer than specified max_duration, " \
+              "ChronoForge:#{name}(#{workflow.key}) job(#{job_id}) executed longer than specified max_duration, " \
               "allowed job(#{current_locked_by}) to acquire the lock."
           end
 

data/lib/chrono_forge/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module ChronoForge
-  VERSION = "0.9.0"
+  VERSION = "0.9.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: chrono_forge
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.9.1
 platform: ruby
 authors:
 - Stefan Froelich
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-06-03 00:00:00.000000000 Z
+date: 2026-06-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord