-
Notifications
You must be signed in to change notification settings - Fork 258
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.
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
update to latest specs #1090
update to latest specs #1090
Conversation
Can you discuss your rational for stating we should ignore the readme when it specifies to use a preview version by default? Isn't this defined by the service owner? (or at least, the spec writer for the service?) |
It could mean a couple of things:
In either case, if there is a stable version, we should use it as our default. |
Here is a complete list. It makes sense that we default to the stable versions. There are 29.
|
While I agree that logically a tag without prerelease in the name should be preferential to a tag with prerelease in the name, I believe this to be more complicated. Consider:
My thought is we probably want to follow the service specification author's specified version and open work items to track things that seem off. |
I changed it back, but made it a warning, so we can raise issues appropriately.
|
This includes a change to pick stable releases if available instead of a spec readme.md that specifies a preview version as the default. They should not be. I included unit tests.
check all features: https://github.com/ctaggart/azure-sdk-for-rust/actions/runs/3016729488