From 151be99ad2a33f2db1e21c91ca85e4a103b3da5c Mon Sep 17 00:00:00 2001 From: Amr Gaber Date: Fri, 22 May 2026 23:21:10 -0500 Subject: [PATCH] =?UTF-8?q?chore:=20revert=20manifest=20version=20bump=20?= =?UTF-8?q?=E2=80=94=20keep=20at=20scaffold=20starter=20(0.1.0)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The version field in a template manifest is the scaffold starter version that new projects inherit when generated from the template, not the template's own release version. Bumping it to 1.0.0 in #28 meant any project scaffolded after that PR would start at 1.0.0 instead of 0.1.0, defeating the purpose of a clean baseline. Reverts package.json to 0.1.0. The template's release history is still tracked via git tags and GitHub Releases — the v1.0.0 tag will be re-pointed to the post-revert HEAD so `git checkout v1.0.0` also gives a 0.1.0 manifest. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index ee3fce8..8909a4b 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "web-template", "private": true, - "version": "1.0.0", + "version": "0.1.0", "type": "module", "engines": { "node": ">=24.0.0"