Releasing clj-physics

This library uses a single source of truth for versions (version.txt) and keeps pom.xml/JARs in sync via make + tools.build.

See CONTRIBUTING.md for versioning rules.

Prerequisites

• Clojure CLI installed.
• Python 3 available (used in Makefile).
• Clojars credentials configured in ~/.m2/settings.xml (server id clojars) or exported as CLOJARS_USERNAME/CLOJARS_PASSWORD.

Release steps

1. Prepare the Codebase

   • Ensure you are on the main branch: git checkout main.
   • Merge development changes: git merge dev (or your feature branch).
   • Ensure the working tree is clean.

2. Set the version

   • Edit version.txt with the new version (e.g., 0.1.2).
   • If new documentation files (manuals/use-cases) were added, ensure they are listed in cljdoc.edn so they appear in the documentation sidebar.

3. Update CHANGELOG.md ...

4. Tag and push

   • Commit changes: git commit -am "Release 0.3.0" (ensure version.txt, CHANGELOG.md, pom.xml are included).
   • Tag: git tag v<version> (e.g., git tag v0.1.2).
   • Push: git push origin main --tags.

5. Verify Documentation

   • Check cljdoc.org/d/net.clojars.helsingin/physics to ensure the version was picked up.
   • If the build doesn't trigger automatically via the GitHub hook, manually request a build for the new version on the cljdoc dashboard.

Notes

• Version is only edited in version.txt.
• make jar always refreshes pom.xml from version.txt.
• Avoid re-deploying a released version; Clojars rejects redeploys for non-snapshots.