ci: fixed branches configuration for semantic-release

semantic-release requires at least one release branch. For simplicity, I'm opting out of creating a separate alpha branch and using a badge to communicate status in the README instead.
goldenpathtechnologies · Mar 13, 2024 · 3591d7a · 3591d7a
1 parent 155e12e
commit 3591d7a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 4 deletions.
diff --git a/README.md b/README.md
@@ -1,5 +1,6 @@
 # hledger-parser
 
+![Project Status](https://img.shields.io/badge/Project_Status-alpha-orange)
 ![NPM Version](https://img.shields.io/npm/v/hledger-parser)
 ![Version](https://img.shields.io/github/package-json/v/goldenpathtechnologies/hledger-parser)
 ![Release](https://img.shields.io/github/actions/workflow/status/goldenpathtechnologies/hledger-parser/release.yml)

diff --git a/package.json b/package.json
@@ -141,10 +141,7 @@
   },
   "release": {
     "branches": [
-      {
-        "name": "main",
-        "prerelease": "alpha"
-      }
+      "main"
     ],
     "plugins": [
       "@semantic-release/commit-analyzer",