Tenacom / ReSharper.ExportAnnotations

MSBuild task to export JetBrains annotations (and optionally strip them) from a compiled assembly.
MIT License
1 stars 1 forks source link

Bump Buildvana.Sdk from 1.0.0-alpha.15 to 1.0.0-alpha.22 #66

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 2 years ago

Bumps Buildvana.Sdk from 1.0.0-alpha.15 to 1.0.0-alpha.22.

Release notes

Sourced from Buildvana.Sdk's releases.

1.0.0-alpha.22

See the changelog for more information.

1.0.0-alpha.21

See the changelog for more information.

1.0.0-alpha.20

See the changelog for more information.

Changelog

Sourced from Buildvana.Sdk's changelog.

1.0.0-alpha.22 (2022-09-22)

New features

  • Quite a few more properties are exported to the external NuSpecFile. The complete list can be seen in the source code. A notable addition is configuration, the only default "nuspec property" missing in Buildvana SDK so far.
  • Files used for the generation of a NuGet package are now shown in Visual Studio's Solution Explorer tree view, under a "virtual" folder named "- Package". This includes: the license file, the third-party notice file, the Readme file, the package icon, and the NuspecFile if specified either explicitly or implicitly (i.e. by having a {ProjectName}.nuspec file in the project folder).
  • When using public API analyzers, TFM-specific public API files are added to the project automatically.

Changes to existing features

  • When generating a NuGet package, previous versions of Buildvana SDK wrote messages to the build log specifying the full paths of license, third-party notice, readme, and icon files. These messages have been removed in favor of showing the files in Visual Studio's Solution Explorer.

Bugs fixed in this release

  • When using an external .nuspec file, the $configuration$ tag did not work in previous versions of Buildvana SDK. This has been fixed.
  • When using an external .nuspec file, the $repositoryType$ tag did not work in previous versions of Buildvana SDK. This has been fixed.

1.0.0-alpha.21 (2022-09-20)

New features

Changes to existing features

  • Buildvana/Buildvana.Sdk#158 - BREAKING CHANGE: The LiteralAssemblyAttributes module has been removed. The CLSCompliant and ComVisible properties, however, are still supported: the corresponding assembly attributes are generated by a source generator.
  • Buildvana/Buildvana.Sdk#158 - BREAKING CHANGE: The ThisAssemblyClass module has been removed. The recommended workaround is to use the ThisAssembly package.
  • Buildvana/Buildvana.Sdk#163 - BREAKING CHANGE: Buildvana SDK does not use or recognize a version file, or otherwise determine a project's version, any longer. The suggested workaround is to use NerdBank.GitVersioning, GitVersion, or any other similar tool.

1.0.0-alpha.20 (2022-05-12)

New features

  • Buildvana/Buildvana.Sdk#142 - For packable projects, Buildvana SDK will automatically find a README.md file and include it in the NuGet package. To disable this feature, set the ReadmeFileInPackage property to false. Recognized names for the README file, in order of lookup, are: Package-README.md; package-readme.md; NuGet-README.md; nuget-readme.md; NuGet.md; nuget.md; README.md; readme.md.

Changes to existing features

  • Buildvana/Buildvana.Sdk#146 - BREAKING CHANGE: The Polyfills module, introduced in v1.0.0-alpha.18, has been removed. Polyfills are a complicated topic, with lots of edge cases. They are best dealt with at a project level. The experience acquired with the Polyfills module has helped shape a polyfill library that will be open-sourced shortly (and is, needless to say, built with Buildvana SDK).
    EDIT: PolyKit has born and is even better than anticipated!

1.0.0-alpha.19 (2022-04-29)

Bugs fixed in this release

1.0.0-alpha.18 (2022-04-26)

New features

... (truncated)

Commits
  • 92b4187 Update changelog and bump version to 1.0.0-alpha.22
  • ca59b46 [FIX] Incorrect package license file link in Solution Explorer.
  • 13b1620 [FIX] TFM-specific public API files are not recognized correctly.
  • 23ab63a Automatically add TFM-specific public API files to projects.
  • 54744c4 Don't add standard public API files to the project. Analyzers already do that.
  • 3370ac9 Show package-related files in Solution Explorer.
  • 7cad3d0 Improve support for external .nuspec files.
  • 30c72c0 Update changelog and bump version to 1.0.0-alpha.21
  • 4f96fe0 Add package type Dependency, otherwise source generators won't be recognized.
  • ba61ef3 Ditch module VersionFile.
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #70.