Skip to content

chore: release v1.0.0#27

Merged
amrtgaber merged 1 commit into
mainfrom
chore/release-v1.0.0
May 23, 2026
Merged

chore: release v1.0.0#27
amrtgaber merged 1 commit into
mainfrom
chore/release-v1.0.0

Conversation

@amrtgaber

Copy link
Copy Markdown
Contributor

First tagged release. Promotes the current state of the template to a v1.0.0 baseline.

The recent /v1 route prefix migration, security backport, production-learnings sweep, and CI runtime modernization together form a coherent stable scaffold worth pinning.

Going forward: manual version bumps on meaningful PRs; release notes via GitHub Releases (no CHANGELOG file).

First tagged release. Promotes the current state of the template to a
v1.0.0 baseline — the recent /v1 route prefix, security backport,
production-learnings sweep, and CI runtime modernization together form
a coherent stable scaffold.

Going forward: manual version bumps on meaningful PRs; release notes
via GitHub Releases (no CHANGELOG file).
@amrtgaber amrtgaber merged commit a0458e1 into main May 23, 2026
2 checks passed
@amrtgaber amrtgaber deleted the chore/release-v1.0.0 branch May 23, 2026 04:08
amrtgaber added a commit that referenced this pull request May 23, 2026
#28)

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant