Skip to content
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 release nuget packages #77261

Merged
merged 3 commits into from
Feb 20, 2025

Conversation

333fred
Copy link
Member

@333fred 333fred commented Feb 18, 2025

In order to publish 17.13 nuget packages, we need to update a few dependencies. I updated the minimum number of packages required from our public packages, then fixed up any restore issues. For each updated package, I then went and confirmed that the dll was actually present in 17.13.0, so we should be safe from dependency loading issues. This change does not need to be inserted into VS.

In order to publish 17.13 nuget packages, we need to update a few dependencies. I updated the minimum number of packages required from our public packages, then fixed up any restore issues. For each updated package, I then went and confirmed that the dll was actually present in 17.13.0, so we should be safe from dependency loading issues. This change does not need to be inserted into VS.
@333fred 333fred requested a review from a team as a code owner February 18, 2025 19:39
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Feb 18, 2025
@333fred 333fred requested a review from a team as a code owner February 18, 2025 22:11
@333fred
Copy link
Member Author

333fred commented Feb 19, 2025

/azp run roslyn-integration-CI

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@333fred
Copy link
Member Author

333fred commented Feb 20, 2025

/azp run roslyn-integration-CI

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@@ -111,7 +111,9 @@ await TestServices.Editor.SetTextAsync(
}

[IdeTheory]
[CombinatorialData]
//[CombinatorialData]
Copy link
Member

Choose a reason for hiding this comment

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

Either delete this or add a comment to go back to CombinatorialData when the skip is removed.

Copy link
Member

Choose a reason for hiding this comment

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

It's also suspicious as everything that one side would work and the other side would not, so if you just want to skip both I'm OK with that.

Copy link
Member

@jasonmalinowski jasonmalinowski left a comment

Choose a reason for hiding this comment

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

Signing off, only comment about how we skipped a test can be done in a follow-up PR, or ignored entirely.

@@ -111,7 +111,9 @@ await TestServices.Editor.SetTextAsync(
}

[IdeTheory]
[CombinatorialData]
//[CombinatorialData]
Copy link
Member

Choose a reason for hiding this comment

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

It's also suspicious as everything that one side would work and the other side would not, so if you just want to skip both I'm OK with that.

@333fred 333fred merged commit 3350036 into dotnet:release/dev17.13 Feb 20, 2025
28 checks passed
@333fred 333fred deleted the update-nuget-packages branch February 20, 2025 19:07
333fred added a commit to 333fred/roslyn that referenced this pull request Feb 20, 2025
* Update to release nuget packages

In order to publish 17.13 nuget packages, we need to update a few dependencies. I updated the minimum number of packages required from our public packages, then fixed up any restore issues. For each updated package, I then went and confirmed that the dll was actually present in 17.13.0, so we should be safe from dependency loading issues. This change does not need to be inserted into VS.

* Skip tests for microsoft/vs-solutionpersistence#95

* Skip failing tests, see dotnet#77293.

(cherry picked from commit 3350036)
333fred added a commit to 333fred/roslyn that referenced this pull request Feb 20, 2025
* Update to release nuget packages

In order to publish 17.13 nuget packages, we need to update a few dependencies. I updated the minimum number of packages required from our public packages, then fixed up any restore issues. For each updated package, I then went and confirmed that the dll was actually present in 17.13.0, so we should be safe from dependency loading issues. This change does not need to be inserted into VS.

* Skip tests for microsoft/vs-solutionpersistence#95

* Skip failing tests, see dotnet#77293.

(cherry picked from commit 3350036)
333fred added a commit that referenced this pull request Feb 20, 2025
* Update to release nuget packages

In order to publish 17.13 nuget packages, we need to update a few dependencies. I updated the minimum number of packages required from our public packages, then fixed up any restore issues. For each updated package, I then went and confirmed that the dll was actually present in 17.13.0, so we should be safe from dependency loading issues. This change does not need to be inserted into VS.

* Skip tests for microsoft/vs-solutionpersistence#95

* Skip failing tests, see #77293.

(cherry picked from commit 3350036)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead VSCode
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants