fix(ci): normalize UTC source commit date across git versions #7

Merged
forgejo-admin merged 1 commit from fix/ci-utc-commit-date into main 2026-10-25 19:32:32 +00:00

git 2.56 (Arch job) prints a UTC committer date as 'Z' via %cI while
git 2.39 (Debian binary-flake job) prints '+00:00'. Forgejo merge
commits are committed in UTC, so arch-build regenerated a different
metadata/release.json and failed matching_tree on every PR merge.
Normalize via datetime.isoformat(), keeping the published '+00:00' form.

Repro: archlinux CI image + publish_arch --prepare on 9791138 fails with "existing build tree/provenance differs"; passes with this patch. python3 -m unittest discover -s ci green (95), new test fails without the fix.

git 2.56 (Arch job) prints a UTC committer date as 'Z' via %cI while git 2.39 (Debian binary-flake job) prints '+00:00'. Forgejo merge commits are committed in UTC, so arch-build regenerated a different metadata/release.json and failed matching_tree on every PR merge. Normalize via datetime.isoformat(), keeping the published '+00:00' form. Repro: archlinux CI image + publish_arch --prepare on 9791138 fails with "existing build tree/provenance differs"; passes with this patch. `python3 -m unittest discover -s ci` green (95), new test fails without the fix.
git 2.56 (Arch job) prints a UTC committer date as 'Z' via %cI while
git 2.39 (Debian binary-flake job) prints '+00:00'. Forgejo merge
commits are committed in UTC, so arch-build regenerated a different
metadata/release.json and failed matching_tree on every PR merge.
Normalize via datetime.isoformat(), keeping the published '+00:00' form.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
forgejo-admin/shluz!7
No description provided.