From fbd1a51f05faa6952a37ff8d0d4a7b7932f35829 Mon Sep 17 00:00:00 2001 From: Tim van der Meij Date: Wed, 10 Jul 2019 23:30:54 +0200 Subject: [PATCH] Updated Release Process (markdown) --- Release-Process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Release-Process.md b/Release-Process.md index 771b6f1..519bc93 100644 --- a/Release-Process.md +++ b/Release-Process.md @@ -9,7 +9,7 @@ 2. Run `python2 release.py {last_pr_number}`, where `{last_pr_number}` is the last PR number (without hash) in the release notes of the existing release 1. Check the box for this release being a pre-release! 1. Label the existing release as stable - 1. Run `npm dist-tag add pdfjs-dist@{stable_version} latest` on the command line to update the `latest` tag on NPM (GitHub's release webhook doesn't seem to trigger edit events) + 1. Run `npm dist-tag add pdfjs-dist@{stable_version} latest` on the command line to update the `latest` tag on NPM (GitHub's release webhook doesn't seem to trigger edit events, which is being reported to GitHub) 1. Update `pdfjs.config` to bump both the stable and beta version numbers: 1. Bump the major/minor version number of the `versionPrefix` 1. Bump the stable/beta version number