You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+26-22Lines changed: 26 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,50 +2,54 @@
2
2
3
3
## Unreleased
4
4
5
-
## [17.2.2] - 2025-11-14
5
+
## v17.3.0 - 2025-12-03
6
+
7
+
- major upgrade of [smqp@11](https://github.com/paed01/smqp/blob/default/CHANGELOG.md)
8
+
9
+
## v17.2.2 - 2025-11-14
6
10
7
11
- npm package provenance release
8
12
9
-
## [17.2.1] - 2025-08-13
13
+
## v17.2.1 - 2025-08-13
10
14
11
15
- major upgrade of [@0dep/piso@3](https://www.npmjs.com/package/@0dep/piso)
12
16
13
-
## [17.2.0] - 2025-07-22
17
+
## v17.2.0 - 2025-07-22
14
18
15
19
- major upgrade of [smqp@10.0.0](https://github.com/paed01/smqp/blob/default/CHANGELOG.md)
16
20
17
-
## [17.1.0] - 2025-04-30
21
+
## v17.1.0 - 2025-04-30
18
22
19
23
- add support for ad-hoc subprocess. The behavior is the same as for an ordinary subprocess
20
24
21
-
## [17.0.0] - 2025-02-08
25
+
## v17.0.0 - 2025-02-08
22
26
23
27
- refactor message formatting, not sure if it breaking or not, but now it behaves as expected when formatting with multiple listeners
24
28
- fix activity discard run when activity has completed executing but not yet reached end, status `executed`
25
29
- use es5 trailing comma
26
30
27
-
## [16.2.2] - 2024-12-26
31
+
## v16.2.2 - 2024-12-26
28
32
29
33
- fix call activities ignoring delegated cancel api message
30
34
31
-
## 16.2.1
35
+
## v16.2.1
32
36
33
37
- fix call activities not represented with `activityStatus=wait`
34
38
- bump [@0dep/piso@2.2](https://www.npmjs.com/package/@0dep/piso) with support for ISO week
35
39
- use optional chaining (?) and nullish coalescing (??) where feasible since it's widely available, in nodejs since v14
36
40
- replace arrays with set and remove unnecessary object assignments
37
41
38
-
## 16.2.0
42
+
## v16.2.0
39
43
40
44
### Breaking
41
45
42
46
- refactor outbound sequence flow evaluation in an attempt to mitigate nasty discard loops when multiple outbound flows have the same target. What happens now is that only one (1) flow will be touched triggering the targeted activity. E.g: all outbound are discarded - only the last discarded flow is discarded; all but one flow is discarded - only taken flow is touched; all flows taken - only the last taken flow is taken. What about conditional flows? No worries, all conditional flows conditions are still evaluated
43
47
44
-
## 16.1.0
48
+
## v16.1.0
45
49
46
50
- support ISO8601 interval timers with unbounded number of repetitions, e.g `R/PT1M` or `R-1/PT1M`
47
51
48
-
## 16.0.0
52
+
## v16.0.0
49
53
50
54
### Breaking
51
55
@@ -57,35 +61,35 @@
57
61
- support conditional event definition condition script
58
62
- export event definitions and flows
59
63
60
-
## [15.0.3] - 2024-07-08
64
+
## v15.0.3 - 2024-07-08
61
65
62
66
- bump [@0dep/piso@2](https://www.npmjs.com/package/@0dep/piso) who totally forgot about applying declared offset before returning date
- make sure message flow targeting process works as expected, successful but was not tested
83
87
84
-
## 14.0.1
88
+
## v14.0.1
85
89
86
90
- throw `RunError` if `TimerEventDefinition` timer value parsing fails, referencing the complaining activity in the error source property
87
91
88
-
## 14.0.0
92
+
## v14.0.0
89
93
90
94
Use [`@0dep/piso`](https://www.npmjs.com/package/@0dep/piso) to parse TimerEventDefinition duration and time date.
91
95
@@ -99,29 +103,29 @@ Use [`@0dep/piso`](https://www.npmjs.com/package/@0dep/piso) to parse TimerEvent
99
103
100
104
- an activity discarded on enter, e.g. discarded by a BoundaryEvent, continued running, that arrogant behavior was unacceptable and stops now
101
105
102
-
## 13.2.0
106
+
## v13.2.0
103
107
104
108
- hoist process environment output to definition environment on process error
105
109
- major update of eslint
106
110
- use prettier for formatting rules, touched basically ALL files
107
111
108
-
## 13.1.2
112
+
## v13.1.2
109
113
110
114
- fix another lingering leave message. Now it was the definition execution that kept `process.leave` messages around for sentimental reasons
111
115
112
-
## 13.1.1
116
+
## v13.1.1
113
117
114
118
- found the real reason behind ever groving state size - `activity.leave` messages were not acked by process execution. Doh!
115
119
116
-
## 13.1.0
120
+
## v13.1.0
117
121
118
122
- introduce `disableTrackState` setting. Tracking of elements is done by counters, e.g. activity taken or discarded, sequence flow taken and discarded. Counters are saved when getting state. If you run really big flows the state will keep all elements just to be able to recover the number of times an element has been touched. Needless to say it the state will grow out of it's comfort zone. Setting `disableTrackState` to true will only return state for elements that are actually running
119
123
120
124
### Breaking
121
125
122
126
-`getState()` can return undefined
123
127
124
-
## 13.0.0
128
+
## v13.0.0
125
129
126
130
- export task-, events-, and gateway activity behaviors through `bpmn-elements/tasks`, `bpmn-elements/events`, and `bpmn-elements/gateways` respectively
127
131
- refactor type definitions for three days to make the above type safe and VS-code happy. Why is it so freaking complicated? Ambient bla bla bla ts(4-digit-number)??? Looped through all 10.000 ts-typescript errors. Patches are inevitable and imminent
0 commit comments