-
Notifications
You must be signed in to change notification settings - Fork 128
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
Initial configuration of revapi to detect API incompatibility. #356
Conversation
@radcortez @kenfinnigan FYI - it can be useful for SmallRye in general |
54c6b02
to
b169b1b
Compare
I'll have a look later. Meanwhile @cescoffier would you put your jbang script somewhere? |
Codecov Report
@@ Coverage Diff @@
## master #356 +/- ##
============================================
+ Coverage 89.29% 89.37% +0.08%
- Complexity 2715 2720 +5
============================================
Files 361 361
Lines 10478 10489 +11
Branches 1302 1304 +2
============================================
+ Hits 9356 9375 +19
+ Misses 583 577 -6
+ Partials 539 537 -2
|
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.
Awesome, does this produce a report in the build output? Does it feed into a release note, maybe?
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.
Definitely a great addition as long as maintenance does not become a nightmare ;-)
@kenfinnigan At the moment, it only generates reports as JSON and also fails the build if there is a non-justified breaking change. From that, I will write a script that collects all the JSON files and build the list to add to the release notes (we already generate the release notes during the release process). At the same time, I will update the json file to "clear" the list of differences. So, when we introduce a breaking change:
BTW, to add a difference, you need to edit a json file, but the content is provided in the build log (Expect the justification, of course) |
@kenfinnigan @jponge I just pushed the JBang script (located in It extracts the breaking changes and generates a markdown file which can be appended to the release notes (not done yet)
It can also clear the differences (after a release for example). It only touches files containing differences with justifications:
Next step is to run these commands during the release. |
Fix the markdown output of the compatibility report.
Release script updated! All done! |
This is great this way! |
That's because of the emojis aka Philippe's touch ;-) |
Emojis are life /cc @k33g |
Configure revapi.
Didn't work on the release tooling yet, but should not be hard.