You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE/servicing_pull_request_template.md
+3-2
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ main PR <!-- Link to PR if any that fixed this in the main branch. -->
22
22
23
23
<!-- Please assess the risk of taking this fix. Provide details backing up your assessment. -->
24
24
25
-
# Package authoring signed off?
25
+
# Package authoring no longer needed in .NET 9
26
26
27
-
IMPORTANT: If this change touches code that ships in a NuGet package, please make certain that you have added any necessary [package authoring](../../docs/project/library-servicing.md) and gotten it explicitly reviewed.
27
+
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
28
+
Keep in mind that we still need package authoring in .NET 8 and older versions.
Copy file name to clipboardExpand all lines: .github/workflows/backport.yml
+4-1
Original file line number
Diff line number
Diff line change
@@ -48,4 +48,7 @@ jobs:
48
48
49
49
- The PR target branch is `release/X.0-staging`, not `release/X.0`.
50
50
51
-
- If the change touches code that ships in a NuGet package, you have added the necessary [package authoring](https://github.com/dotnet/runtime/blob/main/docs/project/library-servicing.md) and gotten it explicitly reviewed.
51
+
## Package authoring no longer needed in .NET 9
52
+
53
+
**IMPORTANT**: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
54
+
Keep in mind that we still need package authoring in .NET 8 and older versions.
Copy file name to clipboardExpand all lines: docs/project/library-servicing.md
+3-8
Original file line number
Diff line number
Diff line change
@@ -8,17 +8,12 @@ Servicing branches represent shipped versions of .NET, and their name is in the
8
8
-`release/7.0-staging`
9
9
-`release/6.0-staging`
10
10
11
-
## Check if a package is generated
12
-
13
-
If a library is packable (check for the `<IsPackable>true</IsPackable>` property) you'll need to set `<GeneratePackageOnBuild>true</GeneratePackageOnBuild>` in the source project. That is necessary as packages aren't generated by default in servicing releases.
14
-
15
-
## Determine ServiceVersion
16
-
17
-
When you make a change to a library & ship it during the servicing release, the `ServicingVersion` must be bumped. This property is found in the library's source project. It's also possible that the property is not in that file, in which case you'll need to add it to the library's source project and set it to 1. If the property is already present in your library's source project, just increment the servicing version by 1.
11
+
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
12
+
Keep in mind that we still need package authoring in .NET 8 and older versions.
18
13
19
14
## Test your changes
20
15
21
-
All that's left is to ensure that your changes have worked as expected. To do so, execute the following steps:
16
+
Develop and test your change as normal. For packages, you may want to test them outside the repo infrastructure. To do so, execute the following steps:
22
17
23
18
1. From a clean copy of your branch, run `build.cmd/sh libs -allconfigurations`
0 commit comments