Make sure API constraints are respected

[pacospace]

Is your feature request related to a problem? Please describe.
As Maintainer,

I would like to have checks between https://github.com/thoth-station/jupyterlab-requirements/blob/master/jupyterlab_requirements/dependency_management/jupyterlab_requirements.yaml and actual API handlers implemented in order to improve testing and make sure failures would not happen across releases.

Describe the solution you'd like

• Introduce logic to verify API constraints from .yaml are matched on the API handlers.

Describe alternatives you've considered

Additional context
Add any other context or screenshots about the feature request here.

[goern]

/kind feature
/triage needs-information

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[goern]

/area byon

[codificat]

This seems to be about adding testing to verify that the extension keeps up to date with API changes

/sig user-experience

[VannTen]

This seems to be about adding testing to verify that the extension keeps up to date with API changes

Another option would be to generate one from the other to make mismatch impossible, if that's possible. (might not be)