TCMProject.Application 26.8.24.1

• net10.0

  • AutoMapper (>= 15.0.1)
  • FluentValidation (>= 12.0.0)
  • FluentValidation.AspNetCore (>= 11.3.0)
  • MediatR (>= 13.0.0)
  • TCMProject.Common (>= 26.5.15.1)
  • TCMProject.Utilities (>= 26.8.22.1)

TCMProject.Application: UnitOfWorkBehaviour now honours [SkipCommandTransaction(true)]. The attribute and its reader (SkipCommandTransaction.GetSkipCommandTransaction<T>) had existed for a long time, but nothing in the codebase ever called the reader: the behaviour wrapped every request whose type name ends in "Command" in a TransactionScope regardless, so the two commands that declared the attribute were still running inside the transaction. It matters for commands with irreversible external side effects: smtpapi's SendPendingEmailCommand sends over SMTP, and a mid-batch failure rolled back the database markers but not the already-sent mail, so the next run found them pending again and re-sent duplicates; paymentsapi's ReceiveGatewayWebhookCommand has the same shape. Holding a transaction open across network I/O also pinned connections and locks needlessly. Behaviour is unchanged for every command that does not declare the attribute (the default is false), and the save path — the nesting counter plus SaveChangesAsync when the outermost level closes — is identical with and without the transaction. Non-breaking. Detected 2026-08-24.