Release automation improvements

- `lein uberjar` builds plain jar & uberjar. We only need the plain jar.
- Simpler release instructions

.github/workflows/release.yml

@@ -20,8 +20,8 @@ jobs:
         lein: latest
     - name: Run tests
       run: lein test
-    - name: Build uberjar
-      run: lein uberjar
+    - name: Build jar
+      run: lein jar
     - name: Deploy to Clojars
       run: lein deploy
       env:

README.md

@@ -109,10 +109,9 @@ These include: `status`, `header`, `file-response`, `content-type`, `find-header
 ## Making a release
 
 - Update `CHANGELOG.md` and increment the version number in `project.clj`
-- Commit
-- Tag with the release number
-- Push to Github
-- Create a Github release by editing the tag you just created on <https://github.com/metosin/ring-http-response/tags>
+- Commit and push to Github
+- Create a Github release [here](https://github.com/metosin/ring-http-response/releases)
+  - Use the version number of the release for the tag name
 - The [Github Actions release workflow](.github/workflows/release.yml) should fire and deploy a release to clojars
 
 ## License