Skip to content

Commit 5e37700

Browse files
authored
Fix typo (#3431)
Downgrades are actually *not* allowed when transitive pinning a package
1 parent 99a9ba8 commit 5e37700

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/consume-packages/Central-Package-Management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ For an idea of how central package management may look like, refer to our [sampl
127127

128128
You can automatically override a transitive package version even without an explicit top-level `<PackageReference />` by opting into a feature known as
129129
transitive pinning. This promotes a transitive dependency to a top-level dependency implicitly on your behalf when necessary.
130-
Note that downgrades are allowed when transitive pinning a package. If you attempt to pin a package to a lower version than the one requested by your dependencies, restore will raise a [NU1109](../reference/errors-and-warnings/NU1109.md) error.
130+
Note that downgrades are not allowed when transitive pinning a package. If you attempt to pin a package to a lower version than the one requested by your dependencies, restore will raise a [NU1109](../reference/errors-and-warnings/NU1109.md) error.
131131

132132
You can enable this feature by setting the MSBuild property `CentralPackageTransitivePinningEnabled` to `true` in a project or in a `Directory.Packages.props`
133133
or `Directory.Build.props` import file:

0 commit comments

Comments
 (0)