From 273ba332beda14f577a1779843b23c5724b7020b Mon Sep 17 00:00:00 2001 From: Amr Gaber Date: Fri, 22 May 2026 23:21:04 -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 #27 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 pyproject.toml 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. --- pyproject.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index 82370c5..14b3de8 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,6 +1,6 @@ [project] name = "api-template" -version = "1.0.0" +version = "0.1.0" description = "FastAPI template with async PostgreSQL and JWT auth" readme = "README.md" requires-python = ">=3.12"