From 67bf6c1a9ab1fce74ff9f6e5e7e11d4fc1f72192 Mon Sep 17 00:00:00 2001 From: root Date: Sun, 26 Apr 2026 00:27:37 +0800 Subject: [PATCH] chore: bump version to v1.7.2.8 --- config/version | 2 +- .../2026-04-26-bump-version-1-7-2-8.md | 29 +++++++++++++++++++ 2 files changed, 30 insertions(+), 1 deletion(-) create mode 100644 docs/Tasktracking/2026-04-26-bump-version-1-7-2-8.md diff --git a/config/version b/config/version index 8a33c5de..ded6d145 100644 --- a/config/version +++ b/config/version @@ -1 +1 @@ -v1.7.2.7 +v1.7.2.8 diff --git a/docs/Tasktracking/2026-04-26-bump-version-1-7-2-8.md b/docs/Tasktracking/2026-04-26-bump-version-1-7-2-8.md new file mode 100644 index 00000000..fdc2cd2a --- /dev/null +++ b/docs/Tasktracking/2026-04-26-bump-version-1-7-2-8.md @@ -0,0 +1,29 @@ +Task Record: + +Date: 2026-04-26 +Related Module: config/version +Change Type: Config + +Background + +A new release tag `v1.7.2.8` is required. The embedded version source still pointed to `v1.7.2.7`, which would cause runtime version output to mismatch the release tag. + +Changes + +Updated `config/version` from `v1.7.2.7` to `v1.7.2.8`. +Added this task tracking record for the version bump and release consistency. + +Impact + +Affected files: `config/version`. +No API, database, runtime logic, or compatibility behavior changes. +Version display and release tag are aligned. + +Verification + +Check: inspected `config/version` content after update. +Result: shows `v1.7.2.8`. + +Risks And Follow-Up + +Low risk. Follow-up is to push commit and `v1.7.2.8` tag to remote repository.