dist.ini

name    = Locale-Simple
author  = Torsten Raudssus <getty@cpan.org>
license = MIT
copyright_holder = Torsten Raudssus L<https://raudssus.de/>
copyright_year = 2026

[@Author::GETTY]
; Run Python + JS test suites alongside `dzil test`.
run_test = python python/test.py
run_test = sh -c 'cd js && npm install --silent --no-audit --no-fund && npm test'

; Before release: rebuild both packages from scratch to catch broken tarballs
; or bundler problems. The Python version bump + build happens HERE (not in
; run_after_release) so Git::Commit picks up the bumped locale_simple.py and
; folds it into the release commit — otherwise the bump sits dirty in the
; working tree until someone commits it by hand.
run_before_release = python python/test.py
run_before_release = sh -c 'cd js && npm install --silent --no-audit --no-fund && npm test'
run_before_release = xbin/release.pl python-prep %v
run_before_release = sh -c 'cd js && npm run build && npm pack --dry-run'

; After release: upload the Python artifacts built in run_before_release.
; JS is published by .github/workflows/publish-js.yml on tag push, via npm
; Trusted Publishing (OIDC) — no token, no OTP, no dzil dependency.
run_after_release = xbin/release.pl python-upload

; Fold the Python version bump done by run_before_release into the release
; commit. @Git::VersionManager exposes `commit_files_after_release` for this
; — it feeds into Git::Commit (release snapshot)'s allow_dirty. Plain
; `Git::Commit.allow_dirty[] = ...` does NOT work as a bundle option.
commit_files_after_release = python/locale_simple.py

[Encoding]
encoding = bytes
match = ^t/data/