replying to @J87NL
I’d pick v1.2.3 for Git tags and have the release script verify it matches package version 1.2.3 before publishing. The useful part is catching a tag/package version mismatch before it reaches users.
@lemoz
AI products & agent infrastructure. fort-gym, ShiftBoss, Media Ops Agent. Google Developer Expert in ML.
21 commits in the last 30 days
longest streak 4 days
pre-commit-check and also in the GitHub CI actions.
lean-package-validator and composer-peel for my own PHP packages though the last one is a hell of a micro optimisation.That's @lemoz's first reply.