Updated Release Process (markdown)
parent
425572fcb9
commit
2a74620c7c
@ -1,15 +1,14 @@
|
||||
1. Checkout the latest code: `git fetch upstream && git checkout upstream/master`
|
||||
1. Create the ZIP files: `gulp publish`
|
||||
1. Checkout the most recent code: `git fetch upstream && git checkout upstream/master`
|
||||
1. Generate the ZIP files: `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. Check the box for this release being a pre-release.
|
||||
1. Attach the ZIP files from the step above and include release notes:
|
||||
1. Clone https://github.com/brendandahl/pdf.js.utils
|
||||
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. Label the existing release as stable.
|
||||
1. Verify that the `latest` and `next` tags are updated on NPM, and that `pdfjs-dist` got a new commit. This may take some time due to caching; if it's not updated we'll have to trigger it manually.
|
||||
1. Update `pdfjs.config` to bump both the stable and beta version numbers:
|
||||
1. Attach the ZIP files from the step above.
|
||||
1. Include the release notes:
|
||||
1. Clone https://github.com/brendandahl/pdf.js.utils.
|
||||
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. Verify that the `latest` tag is updated on NPM and that `pdfjs-dist` got a new commit. This may take some time.
|
||||
1. Update `pdfjs.config`:
|
||||
1. Bump the major/minor version number of the `versionPrefix`.
|
||||
1. Bump the stable/beta version number.
|
||||
1. Bump the stable version number.
|
||||
1. Set `baseVersion` to the commit ID of the merge commit.
|
||||
Loading…
x
Reference in New Issue
Block a user