Skip to content
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

Update dependency org.jetbrains.kotlinx.binary-compatibility-validator to v0.15.1 #216

Merged
merged 1 commit into from
Jul 14, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 8, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.jetbrains.kotlinx.binary-compatibility-validator 0.14.0 -> 0.15.1 age adoption passing confidence

Release Notes

Kotlin/binary-compatibility-validator (org.jetbrains.kotlinx.binary-compatibility-validator)

v0.15.1

Compare Source

What changed:
  • Fixed a regression introduced in 0.15.0 affecting how enum entries from classes with non-public companions are dumped (#​250)

v0.15.0

Compare 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.3
  • Non-public markers are now correctly handled when applied to const vals (#​90, #​245)
  • Fixed KLib dump and validation behavior for empty projects (#​246, #​247); now apiDump will emit an empty file and apiCheck will successfully consume it
From 0.14.0 (brief overview of Beta.1 .. Beta.3 changes)

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.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

github-actions bot commented Jul 8, 2024

Aar size:

Aar size change: +0.0B (210.2KiB -> 210.2KiB)

Diffuse output:

OLD: diffuse-source-file-release
NEW: lazythreetenbp-release.aar

 AAR      │ old       │ new       │ diff 
──────────┼───────────┼───────────┼──────
      jar │  21.2 KiB │  21.2 KiB │  0 B 
 manifest │     203 B │     203 B │  0 B 
    other │     156 B │     156 B │  0 B 
──────────┼───────────┼───────────┼──────
    total │ 164.9 KiB │ 164.9 KiB │  0 B 

 JAR     │ old │ new │ diff      
─────────┼─────┼─────┼───────────
 classes │   6 │   6 │ 0 (+0 -0) 
 methods │  63 │  63 │ 0 (+0 -0) 
  fields │  10 │  10 │ 0 (+0 -0)

@renovate renovate bot force-pushed the renovate/maven.binarycompatiblity branch from 77ac951 to b9bdd16 Compare July 9, 2024 09:06
@renovate renovate bot changed the title Update dependency org.jetbrains.kotlinx.binary-compatibility-validator to v0.15.0 Update dependency org.jetbrains.kotlinx.binary-compatibility-validator to v0.15.1 Jul 9, 2024
@renovate renovate bot force-pushed the renovate/maven.binarycompatiblity branch from b9bdd16 to bd9596e Compare July 14, 2024 08:47
@renovate renovate bot force-pushed the renovate/maven.binarycompatiblity branch from bd9596e to 1a82694 Compare July 14, 2024 08:47
@mateuszkwiecinski mateuszkwiecinski merged commit 716392f into master Jul 14, 2024
3 checks passed
@mateuszkwiecinski mateuszkwiecinski deleted the renovate/maven.binarycompatiblity branch July 14, 2024 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant