RFC 0019: Graduate components from 0.x to v1.0

[thomasmaas]

Summary

• Graduate all 0.x Kuadrant components to v1.0.0 in a single release cycle
• Signals API stability and makes semver meaningful for automation
• No code or API changes — just a version bump
• Components affected: authorino, authorino-operator, limitador-operator, dns-operator, wasm-shim, console-plugin, policy-machinery

Motivation

kuadrant-operator is at v1.4 and limitador at v2.3, but 7 of 9 suite components are still on 0.x despite having stable APIs and production usage. Under semver, 0.x means "anything may change" — which contradicts reality and prevents tooling from trusting version signals.

Test plan

• Review whether each component's API surface is ready for a v1.0 stability commitment
• Discuss timing — should all graduate in the same kuadrant release cycle?
• Decide on wasm-shim and policy-machinery (see unresolved questions)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@thomasmaas has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 57 minutes and 38 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 57 minutes and 38 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e65a6edb-47c3-4254-834a-93bc2c5c30c2

📥 Commits

Reviewing files that changed from the base of the PR and between f521d04 and 391f520.

📒 Files selected for processing (1)

• rfcs/0019-semver-v1-graduation.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rfc/semver-v1-graduation

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[thomasmaas]

Some newer components might not be ready for this move. dns-operator and console-plugin come to mind.

[Boomatang]

I would be on board with this change. The policy-machinery is the only questionable I would have.

[Boomatang]

This can be filled in now.

[Boomatang]

Of every thing, I am not sure about the policy-machinery. That is the one thing that I would call the least stable from the fact we haven't had to do a lot of work there, but that does not mean there is not work needed.

[david-martin]

mcp-gateway is 0.6 right now, soon 0.7.
The plan is to move to 1.0 after that once we move out of tech preview.