yes 2.4.1 → 2.4.3

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.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +32 -0
  3. data/lib/yes/version.rb +1 -1
  4. metadata +9 -9
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: d708f2f63eb4cd742aa3e0398da05a180b249bfb7382046aa7415ac72f71b15d
4
- data.tar.gz: 94463308255bf790fbd74294ce2049a15c06961145b69a7488fa43d343770e04
3
+ metadata.gz: c95eed44962a16b98ab99de78ff8400e374aa6878b9d1e928a8e162ca5b7670d
4
+ data.tar.gz: cce9c158d5ec06cee93ec2252e3312766e4b6a412a1755a117bbd85a3f7fcaef
5
5
  SHA512:
6
- metadata.gz: 76096d51bfee1e241207bf437827b852a678eb7a9ff34e562bd349dc908080b505f492b9b8f5e7ed30506567e48be5401f9726dcd574c9f72e697bdccb3dca30
7
- data.tar.gz: a724df550b48053d33c7c459851f408e5d482f6e4fbeb6b10d889ff473eace370b0d0cca1e0e0d20c943802958f64d5ae0234df59547591c7f48832a3548e4bc
6
+ metadata.gz: 517f1bb10b10a315637c0d8191905a1e54cc2892b9471175e5b0e95fa3fbe88f30752e6e4cc4c75040d1dd92e3620cd888020b99f116298129608b592caabceb
7
+ data.tar.gz: f804b63813efad54dc4c7eeef1481254844a89cdbfc1848cb3c7161db6e312aee0cac4a731c73f3ba8dabc2c16d9e2907f5f37caf7b4705566211980a94047dd
data/CHANGELOG.md CHANGED
@@ -2,6 +2,38 @@
2
2
 
3
3
  All notable changes to this project will be documented in this file.
4
4
 
5
+ ## [2.4.3] - 2026-09-15
6
+
7
+ ### yes-core
8
+
9
+ #### Added
10
+ - `CommandHandling::CommandHandler` and `CommandGroupHandler` record which command they ran on
11
+ the `Execute command` / `Execute command group` span, as a `command` attribute holding the
12
+ command class name (for example `Shop::Order::Commands::Place::Command`). Previously the span
13
+ named only the operation, so a trace showed that a command had run and how many retries it
14
+ needed, but not which command it was. The span name is unchanged on purpose: it is a metric
15
+ dimension, and naming it per command would multiply the latency histogram series per service.
16
+
17
+ ## [2.4.2] - 2026-09-15
18
+
19
+ ### yes-core
20
+
21
+ #### Changed
22
+ - A `PgEventstore::WrongExpectedRevisionError` raised while publishing no longer marks the
23
+ `Publish Event` span as failed. The command executor retries the command, so the conflict is a
24
+ contention signal, not an error: the span keeps a non-error status, records the exception as an
25
+ event and gets `outcome = "revision_conflict"` as an attribute. Any other exception still fails
26
+ the span. Applies to both `CommandHandling::EventPublisher` and the stateless handler's publish.
27
+
28
+ #### Added
29
+ - `OpenTelemetry::OtlSpan::OtlData#tolerated_errors`: a hash of exception class to outcome label.
30
+ A tolerated error is re-raised exactly as before, but the span is not marked as failed and
31
+ carries the label as its `outcome` attribute. `OtlSpan::REVISION_CONFLICT` is the mapping used
32
+ by the publish spans.
33
+ - `CommandExecutor` and `CommandGroupExecutor` stamp the number of retries a command needed on
34
+ the span they run in (`retries` attribute, only when at least one retry happened), so
35
+ per-command contention can be charted from span metrics.
36
+
5
37
  ## [2.4.1] - 2026-09-07
6
38
 
7
39
  ### yes-auth
data/lib/yes/version.rb CHANGED
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Yes
4
- VERSION = '2.4.1'
4
+ VERSION = '2.4.3'
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: 'yes'
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.4.1
4
+ version: 2.4.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Nico Ritsche
@@ -15,56 +15,56 @@ dependencies:
15
15
  requirements:
16
16
  - - '='
17
17
  - !ruby/object:Gem::Version
18
- version: 2.4.1
18
+ version: 2.4.3
19
19
  type: :runtime
20
20
  prerelease: false
21
21
  version_requirements: !ruby/object:Gem::Requirement
22
22
  requirements:
23
23
  - - '='
24
24
  - !ruby/object:Gem::Version
25
- version: 2.4.1
25
+ version: 2.4.3
26
26
  - !ruby/object:Gem::Dependency
27
27
  name: yes-command-api
28
28
  requirement: !ruby/object:Gem::Requirement
29
29
  requirements:
30
30
  - - '='
31
31
  - !ruby/object:Gem::Version
32
- version: 2.4.1
32
+ version: 2.4.3
33
33
  type: :runtime
34
34
  prerelease: false
35
35
  version_requirements: !ruby/object:Gem::Requirement
36
36
  requirements:
37
37
  - - '='
38
38
  - !ruby/object:Gem::Version
39
- version: 2.4.1
39
+ version: 2.4.3
40
40
  - !ruby/object:Gem::Dependency
41
41
  name: yes-core
42
42
  requirement: !ruby/object:Gem::Requirement
43
43
  requirements:
44
44
  - - '='
45
45
  - !ruby/object:Gem::Version
46
- version: 2.4.1
46
+ version: 2.4.3
47
47
  type: :runtime
48
48
  prerelease: false
49
49
  version_requirements: !ruby/object:Gem::Requirement
50
50
  requirements:
51
51
  - - '='
52
52
  - !ruby/object:Gem::Version
53
- version: 2.4.1
53
+ version: 2.4.3
54
54
  - !ruby/object:Gem::Dependency
55
55
  name: yes-read-api
56
56
  requirement: !ruby/object:Gem::Requirement
57
57
  requirements:
58
58
  - - '='
59
59
  - !ruby/object:Gem::Version
60
- version: 2.4.1
60
+ version: 2.4.3
61
61
  type: :runtime
62
62
  prerelease: false
63
63
  version_requirements: !ruby/object:Gem::Requirement
64
64
  requirements:
65
65
  - - '='
66
66
  - !ruby/object:Gem::Version
67
- version: 2.4.1
67
+ version: 2.4.3
68
68
  description: Event sourcing framework for Ruby on Rails applications
69
69
  email:
70
70
  - nico.ritsche@yousty.ch