lightweight tag 6f3c439981365656c503119f395856361d2a5935 v2026.06.17
Author:	github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Date:	Wed Jun 17 18:09:33 2026 +0000

commit 6f3c439981365656c503119f395856361d2a5935
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Date:   Wed Jun 17 18:09:33 2026 +0000

    data: update builds v2026.06.17

commit 1d2552b145489e6cd0a7988b927c66f6679be78d
Author: BAThomp24 <bathomp24@gmail.com>
Date:   Tue Jun 16 20:03:28 2026 -0400

    ci: unique release tags + substitute @project-version@
    
    Two pipeline bugs that stranded the 12.0.7 bump on CurseForge:
    
    1. CurseForge only re-syncs on a NEW release tag — updating the asset on
       an existing tag is silently ignored. The cron created v<date> at 16:00
       UTC; a later same-day push updated the asset but reused the tag, so CF
       never saw the new build. Push/manual runs now append HHMM for a unique
       tag; the cron keeps the clean daily v<date>.
    
    2. @project-version@ was never substituted (our custom pipeline doesn't
       run the CurseForge packager), so the in-game Version field showed the
       literal token. Now sed-substituted with the tag at build time.

