Content Releases: Documents are (apparently) deleted instead of unpublished

[mathiasnovas]

Describe the bug

When scheduling a document for unpublishing ("Unpublish on release"), the document is instead deleted.

To Reproduce

Steps to reproduce the behavior:

1. Select an existing document, or create a new one.
2. Publish the document.
3. Create a new release.
4. Add document to release, and select "Unpublish on release".
5. Navigate to release, and "Run release".

Expected behavior

The published document should be back to a draft once the release is published.

Screenshots

Before "Run release":

After "Run release":

Which versions of Sanity are you using?

@sanity/cli (global)                 3.78.0 (latest: 3.78.1)
@sanity/block-tools                  3.69.0 (latest: 3.70.0)
@sanity/eslint-config-studio          2.0.4 (latest: 5.0.2)
@sanity/hierarchical-document-list    2.0.0 (latest: 2.1.1)
@sanity/icons                         3.5.7 (latest: 3.7.0)
@sanity/locale-nb-no                 1.1.18 (latest: 1.1.19)
@sanity/orderable-document-list       1.2.2 (latest: 1.2.3)
@sanity/react-loader                1.10.34 (latest: 1.10.47)
@sanity/ui                            2.0.0 (latest: 2.15.4)
@sanity/vision                       3.69.0 (latest: 3.78.1)
@sanity/visual-editing               2.12.0 (latest: 2.13.7)
sanity                               3.78.1 (up to date)

Which versions of Node.js / npm are you running?

10.9.2
v22.14.0

[bjoerge]

Hi @mathiasnovas, this should now be fixed so the behavior now match when documents are manually unpublished (fixed on the backend, so upgrading Studio is not required)

Thanks for reporting!