Developer @ Loverde Company
55b65b874d
User wants build numbers to always follow this format, incrementing
<n> across multiple builds on the same calendar day and resetting to 1
on a new day - not a manually-edited fixed string, and not the CI run
counter (which just uploaded a build as '51', unrelated to the real
versioning scheme).
Added next_build_version, which persists {date, build_number} to a
fixed path under this CI user's home directory on the Mac mini runner
(~/ci-build-version-state/pedifoods.json) - state has to live outside
the per-run checkout, since every CI run gets a fresh, throwaway clone
under .cache/act/<random-hash>/. assemble now passes this as the
CURRENT_PROJECT_VERSION xcarg instead of the project's committed value,
so every build gets a fresh, correctly-formatted, ever-increasing
version automatically.
Pedi Foods
This is a private repository.
Read the license
Owner
Any question or doubts, please send thru email
Daniel Arantes Loverde - daniel@loverde.com.br
Clarice Moro Arantes Loverde - clarice@loverde.com.br
Gustavo Moro Arantes Loverde - gustavo@loverde.com.br
Mariana Moro Arantes Loverde - mariana@loverde.com.br
Autor: Daniel Arantes Loverde