Skip to content

Release Process

Tim van der Meij edited this page Jul 25, 2021 · 32 revisions
  1. Checkout the latest code: git fetch upstream && git checkout upstream/master
  2. Create the ZIP files: gulp publish
  3. Create the release on GitHub:
    1. Navigate to https://github.com/mozilla/pdf.js/releases/new.
    2. Call the release and tag v{version} and insert the version from the name of the ZIP file.
    3. Check the box for this release being a pre-release.
    4. 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
    5. Label the existing release as stable.
    6. 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.
  4. Update pdfjs.config to bump both the stable and beta version numbers:
    1. Bump the major/minor version number of the versionPrefix.
    2. Bump the stable/beta version number.
    3. Set baseVersion to the commit ID of the merge commit.
Clone this wiki locally