New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Spec Index to identify versioning issues #8289

Open

weshaggard opened this issue Nov 19, 2024 · 0 comments

Assignees

Labels

Central-EngSys needs-triage

Member

weshaggard commented Nov 19, 2024 •

edited

Loading

We want to update our spec indexing to identify the following:

Places where we have older spec versions left after a stable version has shipped.

This would include all older previews.
Any older stable versions where there was a breaking change. - This case is harder to figure out

Identify places where the version in the spec does not match the version in the path.
Identify places where multiple versions are group together in as a single version in the readme.me

openapi json files don't match the version of the tag
openapi files are a mix of preview and stable
openapi files come from different paths in the repo

cc @JeffreyRichter

weshaggard self-assigned this

weshaggard added the Central-EngSys label

github-project-automation bot added this to Azure SDK EngSys 🚢🎉

github-project-automation bot moved this to 🤔 Triage in Azure SDK EngSys 🚢🎉

github-actions bot added the needs-triage label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment