[ci] Add ApiScan. #829
Merged
[ci] Add ApiScan. #829
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jpobst
force-pushed
the
api-scan
branch
4 times, most recently
from
9e6d44f to
6ccff35
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context: In January of 2024, the EU will begin enforcing the Digital Markets Act, which, for our purposes, means that any high-volume API calls must be documented, or we must switch to using a documented high-volume API.
Microsoft's internal "APIScan" ensures that no undocumented APIs are called.
This scan will be run only on Windows
mainbuilds. Note that APIScan is run on binaries, not code, so it must be run in the build stage rather than the compliance stage.Successful run on a PR build: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=8815822&view=logs&j=2f7369d1-fb97-5262-a571-f4e9c996b7d1&t=df26002c-a356-594f-dc84-ac5f1cd7aaf1
As expected for an open source, cross-platform project, there does not appear to be any issues found that need to be mitigated. 😁