Closed drewrisinger closed 4 years ago
I did not release 4.0.9. The version is marked as a development snapshot. Version 4.0.8 is still the current release because nothing of substance was added. Essentially I only added new unit tests for bugs that do not exist in muparserx.
I'm aware that publishing a new release will trigger a process downstream. For this reason i will only push the button when I think it is justified. At the moment i do not see the need.
Understood. Just got confused by the 4.0.9 language on the master branch/main readme. Thanks for the clarification.
On Sat, Aug 8, 2020, 8:10 PM Ingo Berg notifications@github.com wrote:
I did not release 4.0.9. The version is marked as a development snapshot. Version 4.0.8 is still the current release because nothing of substance was added. Essentially I only added new unit tests for bugs that do not exist in muparserx.
I'm aware that publishing a new release will trigger a process downstream. For this reason i will only push the button when I think it is justified. At the moment i do not see the need.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beltoforion/muparserx/issues/102#issuecomment-670987290, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACNZYI3TZZPUDOUEQMMSGWDR7XSODANCNFSM4PX2ZN5Q .
It looks like you released a v4.0.9 on 2020-06-19, but there is no corresponding tag. Can you create and push one? This makes packaging this for downstream systems easier.