Bump github.com/go-sprout/sprout from 0.4.1 to 0.6.0

[dependabot[bot]]

Bumps github.com/go-sprout/sprout from 0.4.1 to 0.6.0.

Release notes

Sourced from github.com/go-sprout/sprout's releases.

v0.6.0: Sprout Evolution 🌱

💡 Cultivating Precision, One Function at a Time!

🌟 Major Feature: Safe Functions

Now, all functions return errors and follow Go conventions (enforcing the "must" pattern). This ensures you never miss a failure in your template. By default, functions will stop rendering if an error occurs, providing a more predictable and reliable experience. Safe Functions, however, allow you to bypass this strict error handling, letting the template continue rendering even when an error is encountered. This offers flexibility when strict error enforcement is not necessary. See (@​42atomys) PR 65.

Read more about safe functions on official documentation.

🌟 Major Feature: Function Call Notices

Function Call Notices provide feedback or warnings when specific functions are executed, alerting users to potential side effects or special behaviors (like deprecations). This helps ensure more informed decisions during template rendering. See (@​42atomys) PR 58.

Key Benefits:

• User Awareness: Alerts users to important function behavior, such as deprecations or critical warnings, enhancing their understanding without risking breaking an end user's template.
• Easier Debugging: Notices highlight issues in real-time, making it simpler to trace and resolve problems during execution.
• Improved Control: Users gain better insight into function calls, allowing for more deliberate handling of key actions in templates.

Read more about notices on official documentation.

🚀 New Features

• String Capitalization Functions: Added new functions to capitalize strings, fully supporting Unicode and Latin runes. See (@​42atomys) PR 62 and PR 63.
• SHA512 Checksum in Registry: Introduced sha512sum to the checksum registry, complete with informative notices. See (@​42atomys) PR 59.
• hasField for Structs: A new hasField method to check fields in structs is now available. See (@​mbezhanov) PR 61.

🛠 Fixes & Improvements

• Dropped v0.1 Error Handling: Removed legacy error handling until a safe/must decision is finalized in the RFC. See (@​42atomys) PR 52.
• Documentation Updates: Added function signatures to the conventions, making it easier to understand their usage. See (@​42atomys) PR 64.

🐛 Bug Fixes

• Unicode Capitalization Fix: Resolved issues with string capitalization involving Unicode and Latin runes. See (@​42atomys) PR 63.
• Release Candidate Fixes: Addressed problems with v0.6.0-rc.1 to ensure stability and performance. See (@​42atomys) PR 68.

💚 Contributors

• @​mbezhanov made their first contribution in go-sprout/sprout#61

---

🌱🌾⭐ Hit that star button like a space explorer hitting hyperdrive! Stay on board for our next release! 🚀

Release Candidate v0.6.0-rc1 👨‍🌾

We are excited to present the pre-release version, which will be followed by the final release.

The full release note will be available only in the final release.

We would like to express our heartfelt gratitude to all the contributors who have participated in this pre-release by sharing their ideas, feedback, and valuable contributions.

We value and appreciate your input at all times. 💜

v0.5.1: Sprout Growth 🌿

💡 Cultivating Code, Growing Solutions!

... (truncated)

Changelog

Sourced from github.com/go-sprout/sprout's changelog.

Release v0.6.0: Sprout Evolution 🌱 (2024-09-16)

💡 Cultivating Precision, One Function at a Time!

🚀 New Features

• Function Call Notices: Added notifications to inform or warn end-users when functions are called. See PR 58.
• Safe Functions Compliance: Aligned safe functions with Go template standards and Sprout conventions. See PR 65.
• SHA512 Checksum in Registry: Introduced sha512sum to the checksum registry, complete with informative notices. See PR 59.
• hasField for Structs: A new hasField method to check fields in structs is now available. See PR 61.
• String Capitalization Functions: Added new functions to capitalize strings, fully supporting Unicode and Latin runes. See PR 62 and PR 63.

🛠 Fixes & Improvements

• Dropped v0.1 Error Handling: Removed legacy error handling until a safe/must decision is finalized in the RFC. See PR 52.
• Documentation Updates: Added function signatures to the conventions, making it easier to understand their usage. See PR 64.

🐛 Bug Fixes

• Unicode Capitalization Fix: Resolved issues with string capitalization involving Unicode and Latin runes. See PR 63.
• Release Candidate Fixes: Addressed problems with v0.6.0-rc.1 to ensure stability and performance. See PR 68.

Read more about notices on official documentation.

Read more about safe functions on official documentation.

Release v0.5.1: Sprout Growth 🌿 (2024-09-15)

💡 Cultivating Code, Growing Solutions!

⚡ Performance Improvements

• Memory Footprint Reduction: Reduced overall memory footprint for better performance. See (@​42atomys) PR 56.

🐛 Bug Fixes

• Default Logger Initialization: Fixed an issue where the default logger had a bad initialization. See (@​42atomys) PR 48.
• Logger Accessibility: Resolved a problem where loggers were not accessible due to duplicated pointers. See (@​42atomys) PR 50.
• Sprigin CamelCase Consistency: Ensured that sprigin camelcase returns are consistent. See (@​42atomys) PR 55.

🛠️ Chores

• Go Task Integration: Replaced Makefile with Go Task for better task management. See (@​42atomys) PR 54.

Release v0.5.0: Sprout Growth 🌿 (2024-08-15)

💡 Nurturing Ideas, Harvesting Innovation!

🌟 Major Feature: Registry System Unleashed!

• Revamped Architecture: Introducing the powerful registry system (aka loader). This refactor modularizes all methods into separate registries. See (@​42atomys) PR 46
• Handler & Registry Interfaces: New interfaces with clear rules to streamline function management.
• Seamless Migration: All functions are now in registries, with backward compatibility via FuncsMap in springin See Transitioning from Sprig.

Read more about the registry system in the official documentation.

... (truncated)

Commits

• 99a543e chore: prepare v0.6.0 release
• c5fccb4 fix: resolve issues with the v0.6.0-rc.1 (#68)
• b254ec1 docs(gitbook): remove must version part
• 3d90fce docs(gitbook): update roadmap
• 942cb5f docs(gitbook): reflect safe functions feature and new signatures
• 9d3cee5 feat: safe funcs, follow go template standards and sprout conventions (#65)
• e72ad31 docs: add functions signature in conventions (#64)
• e33dad3 fix: capitalize with unicode and latin runes (#63)
• 1eefb84 feat: add strings capitalization functions (#62)
• 44ae526 feat: add hasField method for use with structs (#61)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.