Update vs-solutionpersistence to 1.0.52 #454
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
edvilme
force-pushed
the
vs-solutionpersistence
branch
from
bdba326 to
51e09aa
Compare
mthalman
reviewed
Mar 5, 2025
Member
mthalman
left a comment
mthalman
left a comment
There was a problem hiding this comment.
Can you please provide this info from the PR template:
Provide a link to an issue in the consuming repo describing the need for
the upgrade. Both this PR and the PR doing the upgrade in the consuming repo
should link to that issue.
Contributor
Author
|
Hi @mthalman I updated the description with links to the release and the PRs in the release. Please let me know if that works :) |
Contributor
|
they are asking for links in cosumer repos, like sdk and msbuild, not the source repo |
Member
correct |
mthalman
approved these changes
Mar 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updates vs-solutionpersistence to new release v.1.0.52 with several bug fixes and improvements.
dotnet/sdk#47297
PR Checklist
If you are upgrading the version of a repo submodule, please follow this
checklist:
the upgrade. Both this PR and the PR doing the upgrade in the consuming repo
should link to that issue.
in the consuming repo in a timely manner? If consuming the dependency flow of
this update takes a long time or needs to be backed out, it may require the
reversion of the upgrade in this PR. That's something we want to avoid.
version upgrade, consider using a separate PR or at least changing the title of
the dependency flow PR to accurately reflect the purpose of the change. Seeing
a PR named "Upgrade IdentityModel to 8.0.1", for example, provides better
clarity than "Update dependencies from dotnet/source-build-externals".