From 0c33d0e7ebb00c8156a12774565ef26d6340dd6e Mon Sep 17 00:00:00 2001
From: Tim van der Meij <timvandermeij@gmail.com>
Date: Sat, 2 Nov 2024 20:07:27 +0100
Subject: [PATCH] Updated Release Process (markdown)

---
 Release-Process.md | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/Release-Process.md b/Release-Process.md
index 6a0bd81..6a8239c 100644
--- a/Release-Process.md
+++ b/Release-Process.md
@@ -1,13 +1,17 @@
 1. Make sure there are no [release blockers](https://github.com/mozilla/pdf.js/issues?q=is%3Aopen+label%3Arelease-blocker) before continuing.
-1. Checkout the most recent code: `git fetch upstream && git checkout upstream/master && npm install`
-1. Generate the ZIP files: `npx gulp publish`
+1. Create the release artifacts:
+
+   ```
+   $ git fetch mozilla
+   $ git checkout mozilla/master
+   $ npm install
+   $ npx gulp publish
+   ```
 1. Create the release on GitHub:
     1. Go to https://github.com/mozilla/pdf.js/releases/new.
     1. Name the release and tag `v{version}`, with the version from the name of the ZIP file.
     1. Attach the ZIP files from the step above.
-    1. Write the release notes, using the "Generate release notes" button.
+    1. Write the release notes using the "Generate release notes" button.
     1. Wait until that the `latest` tag is updated on NPM by the GitHub Actions workflow.
-1. Update `pdfjs.config`:
-    1. Bump the stable version number.
-    1. Bump the major/minor version number of the `versionPrefix` and set the `baseVersion` to the commit ID of the merge commit (only if necessary).
+1. Bump the stable version number in `pdfjs.config`:
 1. Share the new release in the Matrix channel.
\ No newline at end of file