[maybebyte]

Summary

copier update targets the latest SemVer tag, so downstreams cannot see the template changes merged since v0.2.0 (the enable_changelog layer and the ruff 0.17 bump) until a release exists. This promotes the Unreleased entries under 0.3.0 so the merge commit can be tagged.

Changes

• Promote the two Unreleased entries to ## [0.3.0] - 2026-10-16 and add the compare link, leaving Unreleased empty (same shape as the v0.2.0 release, docs(changelog): promote the Unreleased entries under 0.2.0 #14).
• Minor bump: the enable_changelog toggle is a new generated-project capability.

Testing

• No automated tests apply (changelog only). Cross-checked against the repo: git log v0.2.0..main -- template copier.yml shows exactly the commits the two entries describe (feat(template): add the enable_changelog layer and dogfood it #26 changelog layer, chore(deps): update dependency ruff to >=0.17,<0.18 #23 ruff 0.17), and no PR merged since v0.2.0 carries the skip-changelog label.

Notes for reviewers

• Merge does not release. After merge, tag the merge commit v0.3.0 (annotated) and push the tag, per the Release section of AGENTS.md; until then downstream copier update still resolves to v0.2.0.