Release ops

FinEngine publish checklist

Use this page before publishing @finengine/core, @finengine/math, and @finengine/ui, and before announcing the repo more broadly.

Verification gates

  1. Run npm run check for site-side JavaScript sanity.
  2. Run npm run verify:packages to build, test, and execute package examples.
  3. Confirm docs pages and homepage examples still match current APIs.
  4. Review responsive behavior on desktop, tablet, and mobile before public sharing.

Publish order

  1. Check versions, exports, README, LICENSE, and dist/ output for @finengine/core.
  2. Publish @finengine/core.
  3. Publish @finengine/math.
  4. Publish @finengine/ui.
  5. Tag the GitHub release and summarize any example/output changes.

Community readiness

  • Issue forms are available for bugs, features, and docs improvements.
  • Pull requests now have a verification checklist.
  • Contribution and conduct guidance should be visible before wider promotion.
  • If you want GitHub Discussions, enable it manually in repository settings and pin a welcome thread.

Launch readiness

  • Keep the website polished first; launch traffic should meet a stable product surface.
  • Prepare Product Hunt assets only when the landing page, screenshots, and positioning are final.
  • Use live GitHub signals, examples, and docs links as proof points.
  • Do not publish until the repo front page and example gallery feel intentional.