yes 2.4.0 → 2.4.2
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 +4 -4
- data/CHANGELOG.md +37 -0
- data/lib/yes/version.rb +1 -1
- metadata +9 -9
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 847e9657b304cd7f838482e25dab5272cafdd5c18c5351e384f33d3d245d85bb
|
|
4
|
+
data.tar.gz: 6688035998ba814857014eb6c5c090b3de7cb3ecc7b3ab43f814a5d65997cdfc
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 32684af33ccef48fcdcd3a8e0b1eacdb3ea7ca3f6aade5a69d14e46a9383da236d739b083ebd269ef2d2d3770876da51ff9460a662ee2654d7cf53449fab82cf
|
|
7
|
+
data.tar.gz: df7fe06911b9f2695d92c6d3c15df796a6d1c2d193d1679a5917b3aaf3ce1f5a36d4eae82c15b0894824bfc159ced01f370d517f43da8113a28754737282072e
|
data/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,43 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
|
|
5
|
+
## [2.4.2] - 2026-09-15
|
|
6
|
+
|
|
7
|
+
### yes-core
|
|
8
|
+
|
|
9
|
+
#### Changed
|
|
10
|
+
- A `PgEventstore::WrongExpectedRevisionError` raised while publishing no longer marks the
|
|
11
|
+
`Publish Event` span as failed. The command executor retries the command, so the conflict is a
|
|
12
|
+
contention signal, not an error: the span keeps a non-error status, records the exception as an
|
|
13
|
+
event and gets `outcome = "revision_conflict"` as an attribute. Any other exception still fails
|
|
14
|
+
the span. Applies to both `CommandHandling::EventPublisher` and the stateless handler's publish.
|
|
15
|
+
|
|
16
|
+
#### Added
|
|
17
|
+
- `OpenTelemetry::OtlSpan::OtlData#tolerated_errors`: a hash of exception class to outcome label.
|
|
18
|
+
A tolerated error is re-raised exactly as before, but the span is not marked as failed and
|
|
19
|
+
carries the label as its `outcome` attribute. `OtlSpan::REVISION_CONFLICT` is the mapping used
|
|
20
|
+
by the publish spans.
|
|
21
|
+
- `CommandExecutor` and `CommandGroupExecutor` stamp the number of retries a command needed on
|
|
22
|
+
the span they run in (`retries` attribute, only when at least one retry happened), so
|
|
23
|
+
per-command contention can be charted from span metrics.
|
|
24
|
+
|
|
25
|
+
## [2.4.1] - 2026-09-07
|
|
26
|
+
|
|
27
|
+
### yes-auth
|
|
28
|
+
|
|
29
|
+
#### Fixed
|
|
30
|
+
- The `auth_principals_*` FactoryBot factories are now included in the released gem.
|
|
31
|
+
They live in `spec/factories`, which no gemspec packaged, so an application that
|
|
32
|
+
installed yes-auth from a gem server got a gem without them while one that resolved
|
|
33
|
+
the same version from git got them on disk. Applications load these factories by
|
|
34
|
+
path to build principals for their own authorization specs, and the usual loader
|
|
35
|
+
guards on the directory existing — so the gem install failed silently at load and
|
|
36
|
+
only surfaced later as `Factory not registered: "auth_principals_user"`.
|
|
37
|
+
|
|
38
|
+
`spec/factories/dummy_resources.rb` stays unpackaged on purpose: it defines generic
|
|
39
|
+
`:company` / `:apprenticeship` / `:location` factories for this gem's own dummy app,
|
|
40
|
+
which would collide with an application's factories of the same name.
|
|
41
|
+
|
|
5
42
|
## [2.4.0] - 2026-09-07
|
|
6
43
|
|
|
7
44
|
### yes-core
|
data/lib/yes/version.rb
CHANGED
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.
|
|
4
|
+
version: 2.4.2
|
|
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.
|
|
18
|
+
version: 2.4.2
|
|
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.
|
|
25
|
+
version: 2.4.2
|
|
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.
|
|
32
|
+
version: 2.4.2
|
|
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.
|
|
39
|
+
version: 2.4.2
|
|
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.
|
|
46
|
+
version: 2.4.2
|
|
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.
|
|
53
|
+
version: 2.4.2
|
|
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.
|
|
60
|
+
version: 2.4.2
|
|
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.
|
|
67
|
+
version: 2.4.2
|
|
68
68
|
description: Event sourcing framework for Ruby on Rails applications
|
|
69
69
|
email:
|
|
70
70
|
- nico.ritsche@yousty.ch
|