Release jev-is-odd

September 18, 2026 ยท View on GitHub

Source repository: robipop22/Jev-is-odd. npm package: jev-is-odd. Always verify the published version with npm view jev-is-odd version; a local build or GitHub push alone does not publish to npm.

  1. Run the live benchmark with a Typesafe key, inspect every incorrect/failed case, and keep its report. Do not market the package as reliable arithmetic.
  2. Create the intended GitHub repository and push this checkout. Keep .env ignored. The folder may retain Jev-is-odd; npm requires the lowercase package name.
  3. Run npm run prepare:release -- https://github.com/OWNER/REPOSITORY. It fills in package repository/homepage/bugs metadata and converts the README artwork URLs to absolute raw GitHub URLs on main, so npm can display them. Commit and push those changes, including package-lock.json. If the default branch differs, update the image URLs accordingly.
  4. Verify the GitHub banner/icon and any metrics image URLs load publicly. Set assets/hero.png as the GitHub social preview if desired; assets/icon.png is the square icon.
  5. Run npm ci, npm run check, npm run test:package, and npm pack --dry-run. Review the included files. Confirm no credentials are present and the remote CI passes.
  6. Check npm whoami and name availability with npm view jev-is-odd. When publication is intended, run npm publish --access public. npm may request two-factor authentication.
  7. Verify npm view jev-is-odd, install from the registry in a fresh directory, and run a keyed smoke test. Record the verified version and evidence in VALIDATION.md.

Do not add tokens to the README, command arguments, GitHub repository, or package contents. For later releases, bump the version with npm version patch (or the appropriate semantic version), inspect the change, and repeat validation before publishing. The package has no automatic publishing workflow.

Source references used to implement the API, checked September 18, 2026: