Updated Release Process (markdown)
parent
ebfecff7d7
commit
0c33d0e7eb
@ -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.
|
||||
Loading…
x
Reference in New Issue
Block a user