b24beadca9
Bpmn.Interchange, Bpmn.Model and Bpmn.Semantics move from 0.1.1-preview.19 to 0.2.0. The three changes below are one unit: the bump is what makes the other two true. Retire the private feed. All three packages are on nuget.org at 0.2.0 -- including Bpmn.Semantics, which had no stable release under 0.1.x. The bpmn-feedz source and its Bpmn.* packageSourceMapping entry both go, which removes a setup step for every consumer. This is not merely cleanup: the feedz feed does not carry 0.2.0 stable, so with the mapping left in place the bump would not restore at all. Restore now resolves Bpmn.* from nuget.org via the existing `*` mapping. Lift IsPackable=false. The comment on the flag named its own removal condition -- the Bpmn.* packages reaching nuget.org -- and that condition is now met, so Elsa.Bpmn and Elsa.Bpmn.Interchange begin shipping. Both pack with every dependency publicly restorable, and both emit a package manifest carrying runtimeKinds ["elsa.server"], so neither is silently excluded from the catalog. They were the last two IsPackable=false projects under src/. Flip the compensation pin to the fixed behaviour. 0.2.0 contains the fix for valence-works/bpmn#13 (filed from here as #7959), so CompensationRunCancelledMidReplay went red on the bump exactly as it was built to. Upstream took the wide fix: every token a cancelled transaction abandons now gets a real teardown. The head handler still starts twice -- that is the release being real -- but the first run is now torn down, so the scope is left holding one live record for the slot instead of two. The applier is deliberately unpatched; the assertions moved to describe the fix, not to accommodate it. Note on persisted state: 0.2.0 freezes the payload format at 1.0.0 and state persisted by 0.1.x no longer deserializes. Elsa persists the library's BpmnExecutionState into workflow state, so an in-flight BPMN instance does not survive this bump. Neither module has ever been published, so no released consumer can be holding such state -- which is why this is the moment to take the break. BpmnRuntimeCapabilitiesTests stays green: 0.2.0 defines no capability flag Elsa does not already declare. The new cancel-end-event requirement is SubtreeCancellation, which BpmnRuntimeCapabilities.Declared already carries. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
31 lines
1.3 KiB
XML
31 lines
1.3 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
|
|
<configuration>
|
|
<packageSources>
|
|
<clear />
|
|
<add key="NuGet official package source" value="https://api.nuget.org/v3/index.json" />
|
|
<add key="cshells-feedz" value="https://f.feedz.io/sfmskywalker/cshells/nuget/index.json" />
|
|
<add key="elsa-preview-feedz" value="https://f.feedz.io/elsa-workflows/elsa-3/nuget/index.json" />
|
|
<add key="valence-loom-feedz" value="https://f.feedz.io/valence-works/loom/nuget/index.json" />
|
|
</packageSources>
|
|
<packageSourceMapping>
|
|
<packageSource key="NuGet official package source">
|
|
<package pattern="*" />
|
|
<package pattern="CShells" />
|
|
<package pattern="CShells.*" />
|
|
</packageSource>
|
|
<packageSource key="cshells-feedz">
|
|
<package pattern="CShells" />
|
|
<package pattern="CShells.*" />
|
|
</packageSource>
|
|
<packageSource key="elsa-preview-feedz">
|
|
<package pattern="Elsa.Platform.PackageManifest.Generator" />
|
|
<package pattern="Elsa.Platform.PackageManifest" />
|
|
</packageSource>
|
|
<packageSource key="valence-loom-feedz">
|
|
<package pattern="Loom" />
|
|
<package pattern="Loom.*" />
|
|
</packageSource>
|
|
</packageSourceMapping>
|
|
</configuration>
|