-
Notifications
You must be signed in to change notification settings - Fork 440
Pin OmniSharp version used for testing #17074
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
Conversation
| public class OmniSharpTests : SmokeTests | ||
| { | ||
| // Update version as new releases become available: https://github.com/OmniSharp/omnisharp-roslyn/releases | ||
| private const string OmniSharpReleaseVersion = "1.39.8"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there anyway we could utilize dependabot to update this for us?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dependabot doesn't support git/GitHub as a source. But apparently Renovate does.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I know Omnisharp also publishes NuGet packages. As a workaround, I thought maybe we could add a package reference and grab it's version from the test. Renovate would work too if we are allowed to use it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interestingly, their NuGet packages are behind from their actual releases by two versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well that's unfortunate. If the low solutions have been exhausted, perhaps we should log a follow-up to automate this. In the meantime would it make sense to add a step to the release checklist?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I'll log a follow-up issue to automate. I can update the release checklist but that's a different repo.
This helps protected the smoke tests from unexpected changes to OmniSharp that may cause the test to break. It pins the version of OmniSharp that is downloaded to use a specific version. This will need to be manually updated as new releases become available.
Also removed a redundant command to set the permissions of the OmniSharp
runscript. This was mistakenly merged in from servicing branches.Fixes dotnet/source-build#3536