v0.3.0 - The "Better Late Than Never"

Release Notes v0.3.0 - The "Better Late Than Never" Edition

Well hello there, that's a bit awkward. We're here with a fresh new update after what seems to be an eternity or just a few years, depending on your perspective. You know, the last time we updated, we think dinosaurs were still roaming around...

We have been maintaining the project but weren't creating releases due to issues with TravisCI, but now we configured Github Actions and we are back on business.

This new update, version 0.3.0, is the equivalent of that forgotten chocolate you discover in the back of the fridge, and it turns out to be utterly delicious. Without further ado, here are the long-awaited changes.

What's changed:

1. In what could be considered a sequel to "War and Peace", @CastixGitHub unraveled the mysteries of issue #117. There was suspense, drama, and finally resolution in pull request #118.

2. @amake came in with a swift uppercut, dropping some knowledge about MacPorts installation in our readme in pull request #121. Applause, everyone! The checksums weren't matching the one we made tho, so @cristianoliveira had to roll it back. We can try again.

3. Tweaking our README.md, because what's a bit of housekeeping between updates, right?

4. We've pushed the Go pedal to the metal with @cristianoliveira bumping the minimal required Go version to 1.18. Vroom vroom! See this in action in pull request #128.

5. @cristianoliveira was on fire, making CI build and upload artifacts on release (pull request #133), run checks on push (pull request #134), and slap on a shiny new CI checks badge (pull request #135).

6. "And it was all yellow"... with integration tests, thanks to @cristianoliveira's stellar performance in pull request #136.

7. In a twist of events, @cristianoliveira delivered a one-two punch with pull requests #137 and #138, allowing any pair configuration and wildcards for services.

New Contributors:

Join us in rolling out the red carpet for our new code-wizards:

• @CastixGitHub, who took their time to introduce a better explanation of the issue with .dev #118.
• @netaskd, who took their to help the window users with documentation #127.

Remember, folks, every code line tells a story, and our new contributors are weaving some fantastic tales.

Here's to another decade before the next release... or hopefully sooner, if the AI doesn't replace us first, we promise! 🎉

For the absolute nerds among us, you can find the full Changelog here.

(Generated with the help of ChatGPT 🤖 😁)