From de7cad5755690dc16122fc90f5cce0bf93581e5e Mon Sep 17 00:00:00 2001 From: oh4 <7767846+iamteedoh@users.noreply.github.com> Date: Thu, 16 Jul 2026 21:04:39 -0400 Subject: [PATCH] DIR-4: let release-please own the version constant --version reported 0.1.0 while the released tag was v0.2.0, and the banner showed the same stale number. The repo releases with release-please's simple strategy, which rewrites versions only on lines carrying an x-release-please-version annotation, and only in files listed under extra-files. VERSION= had neither, so it never moved after 0.1.0 and drifted further with every release. Annotate the constant and declare the script as an extra file, so the version is owned by the release process rather than maintained by hand. Set it to the currently released 0.2.0; the pending release PR now carries it to the version being released. --- dirPathPerms.sh | 5 ++++- release-please-config.json | 8 +++++++- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/dirPathPerms.sh b/dirPathPerms.sh index 5a7f904..7eb401c 100755 --- a/dirPathPerms.sh +++ b/dirPathPerms.sh @@ -11,7 +11,10 @@ set -uo pipefail -VERSION="0.1.0" +# Owned by release-please: the annotation is what makes it rewrite this line on +# a release. Without it the constant never moves and --version quietly reports +# whatever it was first set to. +VERSION="0.2.0" # x-release-please-version # --------------------------------------------------------------------------- # Colors. Disabled when --no-color / $NO_COLOR is set, or stdout is not a TTY diff --git a/release-please-config.json b/release-please-config.json index 0e66b1a..5be6e65 100644 --- a/release-please-config.json +++ b/release-please-config.json @@ -5,7 +5,13 @@ "bootstrap-sha": "b5fe6230d5f86481eb76d4dad58e174f4cfa3c2d", "packages": { ".": { - "package-name": "dirPathPerms" + "package-name": "dirPathPerms", + "extra-files": [ + { + "type": "generic", + "path": "dirPathPerms.sh" + } + ] } }, "include-component-in-tag": false