port19x
commented
5 months ago Hi @Technetium1, the problem is in how we do versioning at ani-cli. Every commit with changes to the ani-cli script that gets merged to master comes with a bump in the patch version. This is even ensured by ci. The minor version gets a bump in one of three scenarios:
- A major outage happens, breaking the script for all users
- A major feature gets added
- Many small commits have accumulated since the last minor bump
Especially that last one is solely in my discretion
For completeness you may wonder when we bump the major version, this only happens after rewrites or source changes.
Now to your concrete problem.
I do agree that patching between releases is unreasonable.
An ani-cli-git package exists for the "bleeding edge" version that is v4.7.6 as of right now.
A new point release is planned after #1274, as there was a fix for windows users a couple PRs prior that we only now know to affect most of them.
I have chimed in at your chaotic aur request, thank you for helpin with it's inclusion there
Make sure you are on the latest version by running
ani-cli -UMetadata (please complete the following information)
Describe the bug
Steps To Reproduce
N/AExpected behavior
4.7.1Should have been tagged and released already as the version was bumped in the commit; however, at this point I believe4.7.2is due as well.Additional context
ani-cliAUR package is unable to get this latest GitHub release to update, and patching between releases would be unreasonable to expect.