Marking Aspire packages as preview and update branding to 2.1 #617
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates versioning information for the upcoming release and marks two packages as pre-release only. The changes ensure that the main version numbers reflect the new release and that specific packages are not published as stable versions.
Versioning updates:
MajorVersion,MinorVersion,PatchVersion, andPreReleaseVersionLabelineng/Versions.propsto reflect the new release (2.1.0-rtw).Pre-release package configuration:
<SuppressFinalPackageVersion>true</SuppressFinalPackageVersion>and set<PreReleaseVersionLabel>preview.1</PreReleaseVersionLabel>insrc/Aspire.Hosting.IncrementalMigration/Aspire.Hosting.IncrementalMigration.csprojto prevent stable package publication.<SuppressFinalPackageVersion>true</SuppressFinalPackageVersion>and set<PreReleaseVersionLabel>preview.1</PreReleaseVersionLabel>insrc/Aspire.Microsoft.AspNetCore.SystemWebAdapters/Aspire.Microsoft.AspNetCore.SystemWebAdapters.csprojto prevent stable package publication.cc: @twsouthwick