Update README and OpenAPI to include prerelease parameter

[jsoriano]

Update README and OpenAPI definition accordingly to the changes in #785.

OpenAPI definition is still most likely outdated in any case, there is another open issue about this (#761).

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-02-24T10:22:33.359+0000

• Duration: 4 min 8 sec

Test stats 🧪

Test	Results
Failed	0
Passed	142
Skipped	0
Total	142

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[andrewkroh]

Could you define what "prerelease versions" means. Like say that it means versions <1.0 and packages using the deprecated beta and experimental release tags (IIRC).

[jsoriano]

Added description. The registry fully relies on semantic versioning to decide if the version of a package is a prerelease, release tags are not considered. This is why it is important to have consistency between release tags and versions till we fully sunset versions that rely on release tags.

[mtojek]

nit: we may consider introducing any logic to validate the openapi.yml. I'm not sure if there is any project using it now.

[jsoriano]

nit: we may consider introducing any logic to validate the openapi.yml. I'm not sure if there is any project using it now.

Yep, we have this issue about validating the definition #761