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

downgrade the System.Text.Json package reference version #1880

Merged
merged 1 commit into from
Sep 22, 2020

Conversation

xuzhg
Copy link
Member

@xuzhg xuzhg commented Sep 10, 2020

Issues

This pull request fixes issue #1878.

Description

Briefly describe the changes of this pull request.

Checklist (Uncheck if it is not completed)

  • Test cases added
  • Build and test with one-click build and test script passed

Additional work necessary

If documentation update is needed, please add "Docs Needed" label to the issue and provide details about the required document change in the issue.

@xuzhg xuzhg force-pushed the downgradeSystemTextJsonVersion branch from 3ecaff7 to e38b1e4 Compare September 10, 2020 17:04
@xuzhg xuzhg force-pushed the downgradeSystemTextJsonVersion branch from e38b1e4 to 257ed02 Compare September 10, 2020 20:57
@xuzhg xuzhg changed the title Add PrivateAsserts to the System.Text.Json package reference downgrade the System.Text.Json package reference version Sep 10, 2020
@xuzhg xuzhg added the Ready for review Use this label if a pull request is ready to be reviewed label Sep 10, 2020
@habbes habbes self-requested a review September 14, 2020 10:58
<PackageReference Include="System.Text.Json">
<Version>4.7.1</Version>
</PackageReference>
<PackageReference Include="System.Text.Json" Version="4.*" />
Copy link
Contributor

@gathogojr gathogojr Sep 15, 2020

Choose a reason for hiding this comment

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

@xuzhg Curious how Version="4.*" is interpreted. Wouldn't 4.7.1 be validated against 4.*?

Copy link
Member Author

Choose a reason for hiding this comment

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

Here's the context:

Floating versions
A floating dependency version is specified with the * character. For example, 6.0.. This version specification says "use the latest 6.0.x version"; 4. means "use the latest 4.x version." Using a floating version reduces changes to the project file, while keeping up to date with the latest version of a dependency.

When using a floating version, NuGet resolves the highest version of a package that matches the version pattern, for example 6.0.* gets the highest version of a package that starts with 6.0:

Choosing version 6.0.1 when a floating version 6.0.* is requested

Copy link
Member Author

Choose a reason for hiding this comment

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

@gathogojr Besides, I use this PR and output a nightly, That nightly can be used directly without the build error.

Copy link
Contributor

Choose a reason for hiding this comment

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

@xuzhg Got it. So having the version pinned to 4.7.1 was the issue

@gathogojr
Copy link
Contributor

@xuzhg Any idea why ADO is reporting building failure for [OData-master-pipeline-Rolling] in spite of this:
image

@habbes
Copy link
Contributor

habbes commented Sep 18, 2020

@xuzhg are the builds failing as a result of this change?

@habbes habbes self-requested a review September 18, 2020 08:39
@mikepizzo mikepizzo added this to the 7.7.2 milestone Sep 21, 2020
@xuzhg
Copy link
Member Author

xuzhg commented Sep 22, 2020

@xuzhg are the builds failing as a result of this change?

No, i run the rolling manually, it can pass. See https://identitydivision.visualstudio.com/OData/_build/results?buildId=621841&view=results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready for review Use this label if a pull request is ready to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants