Fix subversion release having wrong version number

When rsync compares a freshly-built source
against a previously-synced destination, it sees
matching timestamps on both sides and skips any
file whose size also matches, even if the content
differs. The -c flag makes rsync compare MD5
checksums instead, so it correctly detects the
content change.

Author: john-shaffer

CHANGELOG.md

@@ -1,5 +1,7 @@
 ## Unreleased
 
+- Fix subversion release containing wrong version number.
+
 ## 9.9.1 (2026-04-09)
 
 - Fix multiline options in admin did not save properly.

justfile

@@ -71,7 +71,7 @@ _svn-release-version VERSION:
     svn ci "{{ svn_dir }}" --username "{{ svn_user }}" -m "tagging version {{ VERSION }}"
 
 _svn-sync-trunk SRC:
-    rsync -av --delete --chmod=F664,D775 --owner "{{ SRC }}"/* "{{ svn_dir }}"/trunk/
+    rsync -avc --delete --chmod=F664,D775 --owner "{{ SRC }}"/* "{{ svn_dir }}"/trunk/
     svn add --force "{{ svn_dir }}"/trunk/*
 
 # Update subversion repo from WordPress.org