Skip to content

Commit 683ccce

Browse files
Testclaude
andcommitted
docs(changelog): mark v3.3.2 as broken release
The .phar shipped under tag v3.3.2 reports version 3.3.1 because the tag was published against a master commit whose builds/ had never been updated from the rc-3.3.2 branch where CI compiled them. Users installing wtyd/githooks:3.3.2 get the previous release's binary under the new tag's name. Skipping to v3.3.3 with the same fixes correctly bundled. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent e1760b5 commit 683ccce

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

docs/changelog.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,11 @@
22

33
All notable changes to this project are documented here.
44

5-
## [3.3.2]
5+
## [3.3.2] ⚠️ Do not use — broken release
6+
7+
**This release is functionally identical to 3.3.1.** The git tag `v3.3.2` was published against a master commit whose bundled `.phar` binaries (`builds/githooks`, `builds/php7.4/githooks`) had never been updated from the `rc-3.3.2` branch where CI compiled them. Since GitHooks runs as a standalone `.phar`, installing `wtyd/githooks:3.3.2` ships the v3.3.1 binary under the v3.3.2 tag name. The fixes listed below are present in the source code of the tag but **not** in the executed binary.
8+
9+
**Use v3.3.3** — same fixes, correctly bundled.
610

711
### Fixed
812

0 commit comments

Comments
 (0)