Skip to content

Latest commit

 

History

History
14 lines (14 loc) · 1.67 KB

RELEASE_CHECKLIST.md

File metadata and controls

14 lines (14 loc) · 1.67 KB
  1. Go through Github issues to verify bugs have been fixed and closed.
  2. Verify ManifoldCAD.org - check a few examples, run them, download a GLB and a 3MF.
  3. Verify our three.js example is functional.
  4. Verify our model-viewer example is functional - select Union and Intersection.
  5. Verify make-manifold is functional. Try dropping DragonAttenuation.glb in and verify you can select "View Manifold GLB" and that the dragon is still present while the backdrop is removed. Download the GLB.
  6. Make a new branch called the version, e.g. v2.3.0.
  7. Use VSCode to search and replace the old version with the new - so far in test-cmake.sh, flake.nix, pyproject.toml, and package.json.
  8. Also update CMakeLists.txt version by searching for "set(MANIFOLD_VERSION_".
  9. Commit, push, open a PR, verify tests pass, merge.
  10. On Github, draft a new release, make a new tag with the version number, add release notes, and publish.
  11. Check the Actions and verify that both PyPI and npm publishing actions ran successfully.
  12. Verify the npm package looks good - unpacked size should be close to 1MB.
  13. Verify PyPI package looks good - a bunch of built distributions ranging from ~600kB to ~1.1MB.
  14. If there's a problem with release deployment, the release workflows can be triggered separately, manually for any branch, under the Actions tab.