brel 0.3.0 → 0.4.0

package/CHANGELOG.md

@@ -1,3 +1,14 @@
+## [0.4.0] - 2026-02-18
+
+### 🚀 Features
+
+- Add PAT token for tag pushing
+## [0.3.1] - 2026-02-18
+
+### 🐛 Bug Fixes
+
+- Update release & remove facet
+- Changelog prepend
 ## [0.3.0] - 2026-02-18
 
 ### 🚀 Features

package/README.md

@@ -162,6 +162,10 @@ For PRs:
 - Tag format config: `[release_pr.tagging] tag_template = "v{version}"` (default shown).
 - When enabled, the generated workflow listens for merged pull requests into the configured default branch.
 - If the merged PR is managed by `brel` and titled `Release <rendered-tag>`, the workflow validates it against `tag_template`, then creates and pushes that tag when it does not already exist.
+- Create repository secret `BREL_TAG_PUSH_TOKEN` before using tagging-on-merge.
+  - Use a PAT that can push tags to the repository (fine-grained PAT with `Contents: Read and write`).
+  - This is required because pushes done with `GITHUB_TOKEN` do not trigger downstream tag-push workflows.
+- `brel init` prints this secret requirement whenever tagging is enabled.
 
 ## PR Body Templates
 

package/npm-shrinkwrap.json

@@ -23,7 +23,7 @@
       "hasInstallScript": true,
       "license": "MIT",
       "name": "brel",
-      "version": "0.3.0"
+      "version": "0.4.0"
     },
     "node_modules/@isaacs/balanced-match": {
       "engines": {
@@ -515,5 +515,5 @@
     }
   },
   "requires": true,
-  "version": "0.3.0"
+  "version": "0.4.0"
 }

package/package.json

@@ -1,5 +1,5 @@
 {
-  "artifactDownloadUrl": "https://github.com/better-releases/brel/releases/download/0.3.0",
+  "artifactDownloadUrl": "https://github.com/better-releases/brel/releases/download/0.4.0",
   "bin": {
     "brel": "run-brel.js"
   },
@@ -97,7 +97,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.3.0",
+  "version": "0.4.0",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"