From 5b9d2858f507e04cc97a3c206f55d7d5505ae71c Mon Sep 17 00:00:00 2001
From: Bruno Oliveira <bruno@soliv.dev>
Date: Thu, 21 Mar 2024 15:55:40 -0300
Subject: [PATCH 1/2] Release 3.13.0

---
 CHANGELOG.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.rst b/CHANGELOG.rst
index 1c0b69c..d977131 100644
--- a/CHANGELOG.rst
+++ b/CHANGELOG.rst
@@ -1,8 +1,8 @@
 Releases
 ========
 
-UNRELEASED
-----------
+3.13.0 (2024-03-21)
+-------------------
 
 * `#417 <https://github.com/pytest-dev/pytest-mock/pull/417>`_: ``spy`` now has ``spy_return_list``, which is a list containing all the values returned by the spied function.
 * ``pytest-mock`` now requires ``pytest>=6.2.5``.

From ef9461b8b5bdcdd416841b986cf4e1d336c84266 Mon Sep 17 00:00:00 2001
From: Bruno Oliveira <bruno@soliv.dev>
Date: Thu, 21 Mar 2024 15:58:35 -0300
Subject: [PATCH 2/2] Add instructions on how to start deploy from command-line

---
 RELEASING.rst | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/RELEASING.rst b/RELEASING.rst
index 8db6e7c..2c734f1 100644
--- a/RELEASING.rst
+++ b/RELEASING.rst
@@ -3,5 +3,10 @@ Here are the steps on how to make a new release.
 1. Create a ``release-VERSION`` branch from ``upstream/main``.
 2. Update ``CHANGELOG.rst``.
 3. Push the branch to ``upstream``.
-4. Once all tests pass, start the ``deploy`` workflow manually.
+4. Once all tests pass, start the ``deploy`` workflow manually or via:
+
+   ```
+   gh workflow run deploy.yml --repo pytest-dev/pytest-mock --ref release-VERSION -f version=VERSION
+   ```
+
 5. Merge the PR.