-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Do not ship SiteExtension in previews #21786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
...re.AzureAppServices.SiteExtension/Microsoft.AspNetCore.AzureAppServices.SiteExtension.csproj
Outdated
Show resolved
Hide resolved
|
I should probably move this PR to preview5 |
We've generally avoided shipping the SiteExtension in preview releases. I'll file an issue to track re-enabling near the end of 5.0.
2eb795b to
dbe9688
Compare
|
Yes, let's get this in for Preview 5. |
| <NoSemVer20>true</NoSemVer20> | ||
| <IsPackable>true</IsPackable> | ||
| <IsShipping>true</IsShipping> | ||
| <IsShipping Condition=" '$(PreReleaseVersionLabel)' == 'preview' ">false</IsShipping> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, my slight concern for this option is what might happen if we rebrand for an RC release prior to RTM. Should the site extensions ship in that RC?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as we remember, this is of course fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should be fine for an RC
|
Someone with permission please merge 😄 |
We've generally avoided shipping the SiteExtension in preview releases. (Plus the one we did push to NuGet didn't contain the 3.1 bits and was breaking the SiteExtension experience since App Service will just grab the highest versioned package)
I'll file an issue to track re-enabling near the end of 5.0.