From 363afd820bc1c6842f2ab9301ca6c2463071deba Mon Sep 17 00:00:00 2001
From: Ron <theprestig3@gmail.com>
Date: Thu, 3 Sep 2026 12:22:57 +0800
Subject: [PATCH 1/2] ci(release): tag automatically when a release branch
 merges to main

Delegates to the reusable workflow in fleetbase/fleetbase, which validates and
pushes the tag. Accepts release/v0.0.0 and the legacy dev-v0.0.0.
---
 .github/workflows/release.yml | 45 +++++++++++++++++++++++++++++++++++
 1 file changed, 45 insertions(+)
 create mode 100644 .github/workflows/release.yml

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
new file mode 100644
index 0000000..11d1c7f
--- /dev/null
+++ b/.github/workflows/release.yml
@@ -0,0 +1,45 @@
+name: Release Tag
+
+# Tags a release when a release branch is merged to main, and pushes the tag.
+# Delegates to the reusable workflow in fleetbase/fleetbase. Requires org secret
+# _GITHUB_AUTH_TOKEN (inherited); no-ops with a warning until it is set.
+#
+# Branch convention is `release/v0.0.0`; the legacy `dev-v0.0.0` is still accepted so
+# branches opened before the rename still release.
+#
+# It pushes the tag and nothing else — whatever this repository already runs on
+# `push: tags: v*` does the publishing.
+#
+# The version is never retyped: it comes from the branch name, and the tag is refused
+# unless package.json and RELEASE.md already agree with it.
+#
+# RELEASE.md is required, and its first line must name the version being released. That
+# check is the only thing that can tell notes written for this release from the previous
+# release's notes nobody replaced.
+#
+# workflow_dispatch is the recovery path, for when a release fails validation and the fix
+# lands on main after the merge.
+
+on:
+  pull_request:
+    types: [closed]
+    branches: [main]
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Version to tag, e.g. 1.2.3. Recovery only — a normal release reads it from the branch."
+        required: true
+permissions:
+  contents: read
+
+jobs:
+  tag:
+    if: github.event_name == 'workflow_dispatch' ||
+        (github.event.pull_request.merged == true &&
+         (startsWith(github.event.pull_request.head.ref, 'release/v') ||
+          startsWith(github.event.pull_request.head.ref, 'dev-v')))
+    uses: fleetbase/fleetbase/.github/workflows/release-tag.yml@main
+    with:
+      version-files: package.json
+      version: ${{ github.event.inputs.version || '' }}
+    secrets: inherit

From bf6253118985777088ae7c699bf99e616def0e65 Mon Sep 17 00:00:00 2001
From: Ron <theprestig3@gmail.com>
Date: Thu, 3 Sep 2026 12:22:59 +0800
Subject: [PATCH 2/2] docs(release): seed the release notes template

The release workflow refuses to tag unless RELEASE.md's first line names the
version being released. Seeded so that check has something to validate; the
placeholder markers block publishing the template itself.
---
 RELEASE.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 RELEASE.md

diff --git a/RELEASE.md b/RELEASE.md
new file mode 100644
index 0000000..d074f44
--- /dev/null
+++ b/RELEASE.md
@@ -0,0 +1,15 @@
+> v1.1.14 ~ "RELEASE_NOTES_PLACEHOLDER — replace this line with the release title"
+
+---
+## Highlights
+
+RELEASE_NOTES_PLACEHOLDER
+
+Describe what changed in this release. The first line above must name the version being
+released, and both placeholder markers must be gone, or the release workflow refuses to
+tag.
+
+---
+## Need help?
+- [GitHub Discussions](https://github.com/fleetbase/fleetbase/discussions)
+- [Discord](https://discord.gg/HnTqQ6zAVn)