Updated Release Process (markdown)
parent
0c33d0e7eb
commit
286196de9a
@ -1,17 +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. Make sure there are no [release blockers](https://github.com/mozilla/pdf.js/issues?q=is%3Aopen+label%3Arelease-blocker) before continuing.
|
||||||
1. Create the release artifacts:
|
1. Create the release artifacts:
|
||||||
|
|
||||||
```
|
```
|
||||||
$ git fetch mozilla
|
$ git fetch mozilla
|
||||||
$ git checkout mozilla/master
|
$ git checkout mozilla/master
|
||||||
$ npm install
|
$ npm install
|
||||||
$ npx gulp publish
|
$ npx gulp publish
|
||||||
```
|
```
|
||||||
1. Create the release on GitHub:
|
1. Create the release on GitHub:
|
||||||
1. Go to https://github.com/mozilla/pdf.js/releases/new.
|
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. 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. 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. Wait until that the `latest` tag is updated on NPM by the GitHub Actions workflow.
|
||||||
1. Bump the stable version number in `pdfjs.config`:
|
1. Bump the stable version number in `pdfjs.config`
|
||||||
1. Share the new release in the Matrix channel.
|
1. Share the new release in the Matrix channel.
|
||||||
Loading…
x
Reference in New Issue
Block a user