brel 0.2.0 → 0.4.0

package/CHANGELOG.md

@@ -1,8 +1,37 @@
-## [unreleased]
+## [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
+
+- Version_selector dsl
+
+### 💼 Other
+
+- Cargo release
+## [0.2.0] - 2026-02-18
 
 ### 🚀 Features
 
 - Tag after release
+- Tag templating
+
+### 🐛 Bug Fixes
+
+- Changelog generation tag
+
+### ⚙️ Miscellaneous Tasks
+
+- *(release)* V0.2.0
 ## [0.1.2] - 2026-02-18
 
 ### 🐛 Bug Fixes

package/README.md

@@ -80,7 +80,12 @@ When you run `brel release-pr`:
 
 ## How File Updates Work
 
-- `release_pr.version_updates` maps exact repo-relative file paths to dot-separated key paths.
+- `release_pr.version_updates` maps exact repo-relative file paths to selector paths.
+- Selector syntax:
+  - key: `version`
+  - nested key: `package.version`
+  - index selector: `packages[0].version`
+  - filter selector: `package[name=brel].version`
 - Supported file formats:
   - inferred from extension (`.json`, `.toml`)
   - or forced via `release_pr.format_overrides`
@@ -88,13 +93,28 @@ When you run `brel release-pr`:
   - a file is missing,
   - format cannot be determined,
   - parse fails,
-  - a key path does not exist,
-  - target value is not scalar.
+  - a selector is invalid,
+  - a selector matches no values,
+  - a selector uses index/filter on a non-array segment,
+  - a matched value is not a string.
+- Match behavior:
+  - all values matched by a selector are updated
+  - selectors do not create missing keys/paths
 
-Example key paths:
+Example selectors:
 
 - JSON: `"package.json" = ["version", "tooling.release.version"]`
+- JSON with filter: `"package.json" = ["package[name=brel].version"]`
 - TOML: `"Cargo.toml" = ["package.version"]`
+- Cargo.lock (explicit format override required):
+
+```toml
+[release_pr.version_updates]
+"Cargo.lock" = ["package[name=brel].version"]
+
+[release_pr.format_overrides]
+"Cargo.lock" = "toml"
+```
 
 ## Changelog Generation (`git-cliff`)
 
@@ -142,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.2.0"
+      "version": "0.4.0"
     },
     "node_modules/@isaacs/balanced-match": {
       "engines": {
@@ -515,5 +515,5 @@
     }
   },
   "requires": true,
-  "version": "0.2.0"
+  "version": "0.4.0"
 }

package/package.json

@@ -1,5 +1,5 @@
 {
-  "artifactDownloadUrl": "https://github.com/better-releases/brel/releases/download/0.2.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.2.0",
+  "version": "0.4.0",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"