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: CHANGELOG.md
+10-1Lines changed: 10 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
10
10
### New features
11
11
12
12
- A new property `CompletePublishFolderMetadataDependsOn` has been added. The `CompletePublishFolderMetadata` target will depend on targets listed in this property. This is useful to separate concerns among alternate pack methods.
13
+
- The new `ReleaseAssetList` module allows for creation of lists of assets to associate with a release, useful when releases are created externally (GitHub, etc.) and associated assets are the only way to retrieve published artifacts.
14
+
- release asset list generation is enabled by the `GenerateReleaseAssetList` boolean property, defaulting to `true` except in libraries and test projects;
15
+
- to include a file in the release asset list for a project, just add one or more `ReleaseAsset` items;
16
+
- the `Description` metadata of `ReleaseAsset` items can be used to add a textual description of each asset, for CI systems that can use it;
17
+
- release assets without a `Description` metadata are given a default description according to the `DefaultReleaseAssetDescription` property, whose default value is "(no description given)";
18
+
- release asset lists are UTF-8 text files;
19
+
- each row of a release asset list contains the full path of an asset, a tab character (Unicode U+0009), and the asset's description;
20
+
- rows are separated by the build system's line separator (CR+LF on Windows, LF otherwise);
21
+
- each project in a solution generates its own release asset list, whose name can be set via the `ReleaseAssetListFileName` property, defaulting to `$(MSBuildProjectName).assets.txt`;
22
+
- all release asset lists for a solution are placed in the artifacts directory, `$(ArtifactsDirectory)$(Configuration)`.
13
23
- New metadata in `PublishFolder` items allow for zipping a published folder:
14
24
-`CreateZipFile` (boolean) enables the creation of a ZIP file with the contents of the published folder;
15
25
-`ZipFileName` (string) is the name (complete with extension) of the created ZIP file;
@@ -21,7 +31,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
21
31
-`$(MSBuildProjectName)-%(PublishFolder.Identity)_$(BuildVersion).zip` if the `BuildVersion` property is set (such as when using Nerdbank.GitVersioning);
@@ -100,3 +101,9 @@ Each module is assigned a contiguous range of 100 diagnostics, as listed below.
100
101
| Code | Severity | Message | Description |
101
102
| -----| :------: | ------- | ----------- |
102
103
| BVSDK2000 | Error | Version specification JSON file not found. | A `version.json` or `.version.json` file for the project was not found within the repository root. |
0 commit comments