How to re-certify components with new capabilities

Today, a component can be marked as stable after going through conformance and certification tests. On the other hand, there is no clarify on how to proceed when a new capability is added. Should there be a higher bar for adding new features to stable components or should the component have a new version once a new capability is added?

Example: one state store might be certified as stable before it has support to transactions, later on, the transaction capability is added but it might not be as stable as the current code. Should this be a new component version?

No file, test, or entry point is named. Start by reviewing the existing conformance and certification tests and the rules for marking components stable; done means the project has an agreed, documented policy for certifying new capabilities and deciding whether they require a new component version.

Written by the indexing model from the issue text.