Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Hello world! 👋

First of all, thank you very much for all your amazing work on this project!

Issue Description

I’m subscribed to repository notifications for new releases, but I receive a lot of emails because there is a new release for every 2-3 bug fixes. This frequency is overwhelming, especially since many package managers (like Nix) struggle to keep up with this pace.

Proposal: Structured Release Cycles

To improve maintainability and reduce notification fatigue, I suggest adopting a more structured release cycle:

• Fixes (0.0.x):
  Bundle bug fixes into a single release every Sunday evening. This way, users can start their workweek with the latest fixes, and package managers have a predictable schedule to follow.

• Minor (0.x.0):
  Pin a dedicated GitHub issue listing all relevant improvements and features (with links to their respective issues). This makes it easier for new contributors to pick up tasks and ensures transparency about what’s included in each minor release.

• Major (x.0.0):
  Reserve major releases for breaking changes or significant updates, ideally on an annual basis.

Why this approach?

• Reduces email noise for subscribers.
• Aligns with package manager update cycles.
• Encourages community contributions by clarifying priorities.

Let me know what you think! I’m happy to help refine this further if needed.