Marmelator/pdf.js
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated Release Process (markdown)

Tim van der Meij 2024-07-01 18:28:19 +02:00
parent da8b073400
commit 2f5aac66da
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
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.
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).