Skip to content

v6.2.1: Durable-submission action log fix for the 6.2 candidate

The first respin of the 6.2 LTS candidate, which replaces 6.2.0. A Durable entity action no longer loses its “Submitted for durable execution” log row, and two integration checks that failed on every 6.2.0 run now test the right thing. No migrations.

MemberJunction 6.x is released under the Business Source License 1.1; 5.x and earlier stay ISC. What the licence grants, and what needs certification, is in the licence section of the v6 upgrade guide.

  • A durable action’s submission log row survives the save that queued it (@memberjunction/core, @memberjunction/generic-database-provider, @memberjunction/actions, @memberjunction/sqlserver-dataprovider): with a durable submitter registered, an After* Durable entity action runs inside the save’s transaction (#6198), and ActionEngine queued its log row from there. The queued write inherited the transaction, reached SQL after the save had committed and was rejected (The ambient transaction ended before this query ran), so the run left no Action Execution Log row (#6251). BaseEntitySaveQueue gains an opt-in detachFromTransaction option that runs each save outside the caller’s transaction, through the new optional IEntityDataProvider.RunOutsideAmbientTransaction, which GenericDatabaseProvider implements. Only ActionEngine’s log queue turns it on. Other queues (agent run steps, prompt runs, process run details) still join the caller’s transaction, because their owners flush them before commit and their rows reference rows that transaction wrote. (#6351)
  • EW12 expects the full-row GraphQL Update return (@memberjunction/integration-test-suite): the check still asserted the partial return that #6183 replaced. (#6350, #6251)
  • CO20 compares a right and a wrong guess (@memberjunction/integration-test-suite): the check treated any refusal of a comment that quotes a hidden field’s value as a leak, so it failed on every run. The classifier never compares values of fields the comment’s author cannot read, so the refusal does not depend on the hidden value (#6332). CO20 now posts a correct guess and an incorrect one and requires the same outcome: save result, message, recorded restricted fields and what the reader can see. It also pins the LLM stage to “no match” for the whole check. (#6379)
  • Upgrade every MemberJunction package to 6.2.1 together. There are no migrations. Nothing changes for 6.2.0 installs beyond the fixes above.