-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Add missed packages to packages.builds for 2.1.5 #32203
Changes from all commits
b49d81a
ffc963b
6056b1d
4e4dc12
0e84b39
0173b41
194c1ab
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,7 +2,8 @@ | |
| <Project ToolsVersion="14.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> | ||
| <Import Project="..\dir.props" /> | ||
| <PropertyGroup> | ||
| <AssemblyVersion>4.0.0.0</AssemblyVersion> | ||
| <AssemblyVersion>4.0.0.1</AssemblyVersion> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @natemcmaster FYI we are bumping the assembly version of System.IO.Pipelines for 2.1.5 servicing. |
||
| <PackageVersion>4.5.2</PackageVersion> | ||
| <AssemblyKey>Open</AssemblyKey> | ||
| </PropertyGroup> | ||
| </Project> | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,7 +2,8 @@ | |
| <Project ToolsVersion="14.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> | ||
| <Import Project="..\dir.props" /> | ||
| <PropertyGroup> | ||
| <AssemblyVersion>4.0.3.0</AssemblyVersion> | ||
| <AssemblyVersion>4.0.3.1</AssemblyVersion> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Presumably we should just close #32111 and take this as the "fix everything" change?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I suspect so.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @weshaggard do I also need to update packageIndex.json with the new
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I suspect you might. You will hopefully figure out when the all configuration leg fails. |
||
| <PackageVersion>4.5.1</PackageVersion> | ||
| <AssemblyKey>MSFT</AssemblyKey> | ||
| </PropertyGroup> | ||
| </Project> | ||
Uh oh!
There was an error while loading. Please reload this page.
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.
The assembly version's package version should be the one in which the assembly with the given version shipped the first time. In this case 4.5.0 and not 4.5.1. Same for others below/above.
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.
No it should be the latest package that shipped stable. We want to ensure that folks are getting the latest version of any changes with the same assembly version.
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.
hmm makes sense but @ericstj told me the opposite in a random PR which I can't find right now.