fix(deps): update binary.compatibility.validator to v0.18.1#696
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
fix(deps): update binary.compatibility.validator to v0.18.1#696renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #696 +/- ##
=======================================
Coverage 80.17% 80.17%
=======================================
Files 42 42
Lines 928 928
Branches 177 177
=======================================
Hits 744 744
Misses 110 110
Partials 74 74 🚀 New features to boost your workflow:
|
c59780f to
edc6034
Compare
edc6034 to
a157cd3
Compare
a157cd3 to
711fc68
Compare
711fc68 to
f397f8e
Compare
f397f8e to
1004b60
Compare
1004b60 to
aab1ebe
Compare
aab1ebe to
0d9d06b
Compare
0d9d06b to
f1b7340
Compare
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
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.
This PR contains the following updates:
0.15.0-Beta.2→0.18.10.15.0-Beta.2→0.18.1Release Notes
Kotlin/binary-compatibility-validator (org.jetbrains.kotlinx.binary-compatibility-validator)
v0.18.1Compare Source
What's Changed
v0.18.0Compare Source
What's Changed
Thanks to @TheMrMilchmann, @osipxd, and @Goooler for their contributions!
v0.17.0Compare Source
What's Changed
$suspendImplfunctions are now filtered from dumps (#271)This change may cause validation failures for projects where dumps already contain such functions. It is recommended to regenerate dumps (
apiDumptask) after updating the BCV to0.17.0.v0.16.3Compare Source
What's Changed:
8.2(#263)v0.16.2What's Changed:
v0.16.0Compare Source
What changed:
kotlin-metadata-jvm:2.0.0) #255v0.15.1Compare Source
What changed:
0.15.0affecting how enum entries from classes with non-public companions are dumped (#250)v0.15.0Compare Source
This release finalizes what was added in the series of beta releases and adds Kotlin libraries (KLib) dumping and validation support.
See project's README for details on how to enable it for your project.
The release contains some breaking changes that were made to align and fix BCV behavior across all supported configurations:
If any of these changes affect your projects, please check the migration guide for details on what needs to be done to update BCV to 0.15.0: 0.15.0 Migration Guide.
What changed:
From
0.15.0-Beta.3const vals (#90, #245)apiDumpwill emit an empty file andapiCheckwill successfully consume itFrom
0.14.0(brief overview of Beta.1 .. Beta.3 changes)List<ClassBinarySignature>.dumpnow sorts declarations the same way the Gradle task does (#188)I want to give a shout-out to everyone involved! Special thanks to @benedekh, @adam-enko, @JakeWharton, @rickclephas, @lukellmann, @illarionov, @sandwwraith, @martinbonnin, @ilya-g and @shanshin for their feedback and contributions.
v0.15.0-Beta.3Compare Source
This release provides updated KLib validation support and fixes some previously reported KLib-related issues.
The release contains some breaking changes that were made to align and fix BCV behavior across all supported configurations:
Propertiesinstead of plain Kotlin properties.If any of these changes affect your projects, please check the migration guide for details on what needs to be done to update BCV to
0.15.0-Beta.3: 0.15.0 Migration Guide.Compared to
0.15.0-Beta.2, the KLib ABI dump file format was changed to be more readable (#196, #197). The newer BCV version will successfully validate the ABI against golden dump files generated by previous versions, but the execution of theapiDumptask will result in updated.klib.apifiles even if the ABI itself remains the same. Thus, it's recommended to update the plugin and dump files separately from changes affecting your code.What changed:
ignoredProjects.KlibSignatureVersion.toStringformat (#219, #220)apiValidation.klibextension Groovy-friendly (#214, #215)Thanks to everyone who tried KLib validation support. Special thanks to @JakeWharton, @illarionov, @aSemy, @sandwwraith for your feedback and suggestions!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.