-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Fix API baseline check when building site extensions #27841
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
Tested in the PR build to ensure the fix is sufficient. Not sure what the value is in including API files for the HostingStartup project. I think it would make more sense to disable the check instead. But given that the API baseline files are present, I've chosen to include the files for the build. Note that currently release/5.0 is blocked on this. |
I'm going to merge this now to fix the build, but I'll address feedback separately if needed. |
Turns out I can't force merge. I guess I'll wait for review. |
@JunTaoLuo this will work but you're right API baselines for tools aren't useful. Since this project doesn't follow the usual conventions, I recommend removing the PublicApi.*.txt files then adding the following to HostingStartup.csproj
That matches what I did for other tools that don't have |
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.
If you want to save time and go with this approach, 🆗 Please follow up with a correction afterward in that case.
I'll disable the check |
Hello @JunTaoLuo! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
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.
Thanks @JunTaoLuo❕ Please revert your ci.yml change before merging.
Let's also remember to discuss the annoyance of PR validation not building the site extensions in Teams w/ our leads on Monday or at the meeting on Thursday.
Oops I was looking at an old view of the PR. The src/SiteExtensions/Sdk/SiteExtension.targets change should be reverted in release/5.0 because it's just confusing. |
Try to fix 5.0 builds.