(v1.0.2) added new github workflow

.github/workflows/deploy.yml

@@ -0,0 +1,27 @@
+name: NPM Deploy
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v2
+        with:
+          node-version: '18'
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Publish to npm
+        run: npm publish --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_AUTH_TOKEN }}

package.json

@@ -1,10 +1,13 @@
 {
   "name": "@reyco1/release-notes",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "Generates formatted release notes from Git commit logs using OpenAI's API.",
   "main": "index.js",
   "private": false,
   "type": "module",
+  "engines": {
+    "node": ">=18.0.0"
+  },
   "bin": {
     "release-notes": "./index.js"
   },

prompt.txt

@@ -2,7 +2,7 @@ Steps to Format Git Commit Logs into Release Notes:
 
 1. Input Preparation:
     - User will provide all commit logs relevant for the release notes.
-    - Ensure each log entry follows the standard format: "(v[version number]) [Commit message]".
+    - Ensure each log entry follows the standard format: "[dateTime] (v[version number]) [Commit message]".
 
 2. Summary Creation:
     - Begin by summarizing the main achievements or features introduced in this batch of commits. Highlight any major enhancements, critical bug fixes, or significant performance improvements.

version.json

@@ -1,5 +1,5 @@
 {
     "major": 1,
     "minor": 0,
-    "patch": 1
+    "patch": 2
 }