Skip to content

Conversation

@mthalman
Copy link
Member

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 run script. This was mistakenly merged in from servicing branches.

Fixes dotnet/source-build#3536

@mthalman mthalman requested a review from a team as a code owner July 26, 2023 21:10
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";
Copy link
Member

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?

Copy link
Member Author

@mthalman mthalman Jul 27, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dependabot/dependabot-core#1743.

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.

Copy link
Member Author

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.

Copy link
Member

@MichaelSimons MichaelSimons Jul 27, 2023

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?

Copy link
Member Author

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.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Risk of being broken by new releases of OmniSharp

3 participants