ci: cleanup semantic release

.github/pull_request_template.md

@@ -1,13 +1,9 @@
-<!-- PRS-123: Short description of change -->
-
 ## Description
-<!-- A longer description of the change -->
 
 ## Issue
 - [ ] :clipboard: JIRA_TICKET_URL
 
 ## Screenshots
-<!-- If relevant -->
 
 ## PR Readiness Checks
 - [ ] Your PR title conforms to conventional commits `<type>: <jira-ticket-num><title>`, for example: `fix: PRSDM-123 issue with login` with a maximum of 100 characters

.github/workflows/semantic-pull-request.yml → .github/workflows/lint-pr-title.yml

@@ -1,4 +1,4 @@
-name: "Lint PR"
+name: "Lint PR Title"
 
 on:
   pull_request:

.releaserc.json

@@ -0,0 +1,44 @@
+{
+  "branches": ["main", { "name": "develop", "prerelease": "rfv" }, "+([0-9])?(.{+([0-9]),x}).x"],
+  "plugins": [
+    ["@semantic-release/commit-analyzer",
+      {
+        "releaseRules": [
+          {
+            "type": "refactor",
+            "release": "patch"
+          }
+        ]
+      }
+    ], 
+    ["@semantic-release/release-notes-generator",
+      {
+        "presetConfig": {
+          "types": [
+            {
+              "type": "refactor",
+              "section": "Refactors",
+              "hidden": false
+            }
+          ]
+        }
+      }
+    ],
+    ["@semantic-release/exec",
+      {
+        "prepareCmd": "zip -r -qq presidium-js dist"
+      }
+    ],
+    ["@semantic-release/github",
+      {
+        "assets": [
+          {
+            "path": "presidium-js.zip",
+            "name":"${nextRelease.gitTag}.zip",
+            "label": "${nextRelease.gitTag}.zip"
+          }
+        ]
+      }
+    ]
+  ]
+}

README.md

@@ -46,7 +46,7 @@ make commitlint
 
 ### Usage
 
-After installation you can use `git cz` and run through the options and it will build your commit message. For example:
+After installation you can use `git cz` and run through the options, it will build your commit message. For example:
 
 ```
 ? Select the type of change that you're committing: refactor: A code change that neither fixes a bug nor adds a feature (formatting, performance improvement, etc)
@@ -90,10 +90,9 @@ This repository uses [Semantic Release](https://semantic-release.gitbook.io/sema
 
 Upon merging into to the main or develop branch, Semantic Release tool will:
 - Calculate the new release version based on the commits
-- Generate the CHANGELOG file
-- Update the VERSION file
 - Create a git commit and a git tag for the release
-- Create a Release on Github
+- Create a Release with release notes from the commit messages
+- Create and publish the container images
 
 ---
 
@@ -102,11 +101,11 @@ Upon merging into to the main or develop branch, Semantic Release tool will:
 Please see this [Presidium Git Strategy Miro board](https://miro.com/app/board/uXjVPK0XxiU=/).
 
 In summary:
-- `main` -> production
+- `main` ⇾ production
   - Only hotfixes or `develop` get merged into `main`
 - `develop`
-  - Feature branches and bugfixes are branched from and merged into `develop`
-- `feat: <TITLE>`
+  - Feature branches and bug fixes are branched from and merged into `develop`
+- `feat/<TITLE>`
   - If there is a feature in development it will be on a feature branch
 
 ---