Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.274,
Internal ChangesSection of the release
What
The artifact publish "version" action, along with its three underlying implementations (workshop files-only publish, live-doc publish, and the general publish path), now pass a requestId taken from the incoming request through to the backend publish call.
Why
Threading a request ID through publish calls supports idempotency, meaning a repeated or retried publish request can be recognized as the same request rather than causing a duplicate action.
