From 2f5aac66da05c300bbb6622611ea368687d37cd0 Mon Sep 17 00:00:00 2001 From: Tim van der Meij Date: Mon, 1 Jul 2024 18:28:19 +0200 Subject: [PATCH] Updated Release Process (markdown) --- Release-Process.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/Release-Process.md b/Release-Process.md index c1cd6ad..4097ae0 100644 --- a/Release-Process.md +++ b/Release-Process.md @@ -1,13 +1,12 @@ 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` +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 on GitHub: - 1. Navigate to https://github.com/mozilla/pdf.js/releases/new. - 1. Call the release and tag `v{version}` and insert the version from the name of the ZIP file. + 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 for the commits. - 1. Verify that the `latest` tag is updated on NPM and that `pdfjs-dist` got a new commit. This may take some time. + 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 major/minor version number of the `versionPrefix`. 1. Bump the stable version number. - 1. Set `baseVersion` to the commit ID of the merge commit. \ No newline at end of file + 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). \ No newline at end of file