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
Add API validation script to CI #1026
Comments
Happened to find https://github.com/ltetzlaff/swift-api-diff today. Don't suppose SwiftNIO is looking at make a standard github action out of this? |
The script also needs |
If the community has already done a standard GitHub action I'm more than happy to defer to that! |
Since it seems to have a copy of the script, i wasn't sure how insync it is staying, etc. Is there any coordination with them? |
It also looks like it posts back to the comments, which means it needs a github token. That likely means someone on Apple's side would need to sign off on it before we could use it here. @tbkka I'm guessing the need for a secret to post back means it shouldn't be used here? |
Also looks like despite the script having (I was looking to wire up a Makefile rule for running it, but it would be linux only.) |
@thomasvl -- Yeah, we should avoid anything that needs a secret to post back. |
@Lukasa should I open a nio issue asking for a standard action that doesn't require write access? |
@thomasvl Sure, worst-case we can say we think it's out of scope. But I think an action is a nice approach. |
Opened apple/swift-nio#1600 |
Just run this on each PR to flag any changes. Since `main` is working toward a 2.0 release, we should be ok making breaking changes, but it likely doesn't hurt to realize what the breaks are. Fixes apple#1026
Just run this on each PR to flag any changes. Since `main` is working toward a 2.0 release, we should be ok making breaking changes, but it likely doesn't hurt to realize what the breaks are. Used some of the https://github.com/vapor projects for reference and the git magic needed to for the action to run. Fixes apple#1026
Just run this on each PR to flag any changes. Since `main` is working toward a 2.0 release, we should be ok making breaking changes, but it likely doesn't hurt to realize what the breaks are. Used some of the https://github.com/vapor projects for reference and the git magic needed to for the action to run. Fixes apple#1026
Just run this on each PR to flag any changes. Since `main` is working toward a 2.0 release, we should be ok making breaking changes, but it likely doesn't hurt to realize what the breaks are. Used some of the https://github.com/vapor projects for reference and the git magic needed to for the action to run. Fixes apple#1026
Just run this on each PR to flag any changes. Since `main` is working toward a 2.0 release, we should be ok making breaking changes, but it likely doesn't hurt to realize what the breaks are. Used some of the https://github.com/vapor projects for reference and the git magic needed to for the action to run. Fixes apple#1026
Just run this on each PR to flag any changes. Since `main` is working toward a 2.0 release, we should be ok making breaking changes, but it likely doesn't hurt to realize what the breaks are. Used some of the https://github.com/vapor projects for reference and the git magic needed to for the action to run. Fixes #1026
SwiftNIO uses a script built on top of the Swift API digester command line tool to validate that PRs do not cause semver major breaking changes. This script could be adapted for the use cases of protobuf as well, and help avoid ambiguity around whether a change is breaking or not.
Note that, while this script is helpful, it does encounter some false positives. In particular it tends to believe that adding a protocol customisation point with a default implementation is a semver major, when so far as we can tell it is not (it's ABI breaking, I think, but not a semver major).
The text was updated successfully, but these errors were encountered: