Establish release cadence / tagging strategy for CRDs-catalog

[reiinoldo]

Hello 👋

Currently, the latest release of this repository is quite old. I am using kubeconform together with this catalog (referencing main), but since main changes immediately on merge, it can introduce breaking changes in validation unexpectedly.

For instance, PR #659 was merged and caused validation failures. @Moglum even suggested a revert because of the breakage. Having tagged releases would have prevented this, as users could stay on a stable tag until ready to adopt the new schema changes.

• Pin to a stable release for production validation.
• Decide when to bump to a newer release and handle schema changes deliberately.
• Avoid unexpected validation failures when consuming main directly.

Proposal:

• Introduce a regular release cadence (e.g., monthly/quarterly) or-
• Tag releases whenever significant schema updates are merged.

This would make it much easier to consume the catalog safely in CI/CD pipelines and improve long-term maintainability.

Thanks a lot for your work on this repo 🙏

[userbradley]

I think this would be a great use case for something like release please on a weekly schedule. It manages both the changelog as well as tagging and releasing.