is this still supported? about sprig

[42atomys]

Exploring sprig for my projects, I've noticed it could benefit from updates and additional features. With this in mind, I'm developing an evolved version, sprout, to address these gaps by leveraging new Go functionalities and minimizing dependencies. This project aims to build on sprig’s legacy, maintaining compatibility with sprig v3.2.3 while planning for future enhancements.

@caarlos0, your insights could greatly benefit this initiative. Would you be interested in collaborating on sprout? Our goal is to offer a seamless transition for sprig users, enriching the library with more capabilities over time. Check out sprout v0.1 for a glimpse of our foundation, promising no breaking changes with the potential for significant future growth.

I will start to add features from sprig issues and PR in few days (also because I need somes features for my projects).

Important

The fork has a new home https://github.com/go-sprout/sprout. Feel free to join !

See You All 💜

[andig]

Per issue template:

<!--
Thank you for submitting an issue to sprig.

If you have a feature request than pull requests for those features are also appreciated.

Sprig is a maintained project. Triaging issue happens several times per year rather than daily or weekly.
-->

But it seems that a year has passed now.

[caarlos0]

hey @42atomys, yes, happy to help 🙏

[42atomys]

@caarlos0 awesome, I have created the issue one 42atomys/sprout#1 to discuss and collaborate all together 🚀

All others developers are welcome to grow together 🌱

[andig]

@mattfarina I've noticed you're still active in https://github.com/Masterminds/semver. A statement would be great if you want 👍🏻

[42atomys]

This is why we ask and we start to maintain to free time to the creator and give faster feedback to devs 🍕