Skip to content

Conversation

@skydoves
Copy link
Owner

@skydoves skydoves commented Nov 10, 2025

Prepare for release 0.5.1.

Summary by CodeRabbit

Release Notes - Version 0.5.1

  • New Features

    • Added wasmJs target support to stability-runtime.
  • Bug Fixes

    • Improved sealed class hierarchy handling consistency between IDE and compiler plugins.
  • Chores

    • Updated project version to 0.5.1.

@skydoves skydoves self-assigned this Nov 10, 2025
@coderabbitai
Copy link

coderabbitai bot commented Nov 10, 2025

Warning

Rate limit exceeded

@skydoves has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 27 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between bc86609 and 1686c03.

📒 Files selected for processing (1)
  • compose-stability-analyzer-idea/build.gradle.kts (1 hunks)

Walkthrough

This is a version bump release PR that increments Stability Analyzer from 0.5.0 to 0.5.1 across documentation, build configuration, and plugin code. The CHANGELOG documents new wasmJs target support and stability annotation fixes for sealed classes.

Changes

Cohort / File(s) Summary
Documentation & Release Notes
README.md, CHANGELOG.md
Updated README example dependency version from 0.5.0 to 0.5.1; added Kotlin 2.2.21 mapping table row. Added new 0.5.1 release section to CHANGELOG documenting wasmJs target support and sealed class hierarchy consistency fixes.
Build Configuration
gradle.properties
Incremented VERSION_NAME property from 0.5.0 to 0.5.1.
Plugin Code
stability-gradle/src/main/kotlin/com/skydoves/compose/stability/gradle/StabilityAnalyzerGradlePlugin.kt
Updated internal plugin version constant from "0.5.0" to "0.5.1" used for compiler plugin artifact construction.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Simple, repetitive version bump across multiple files with no logic changes
  • Verify version consistency across all files and that CHANGELOG entries accurately reflect feature additions

Possibly related PRs

  • #15: Updates the same VERSION constant in StabilityAnalyzerGradlePlugin.kt for a release version bump
  • #30: Changes the same version constants and release metadata across compiler plugin and build configuration
  • #27: Modifies StabilityAnalyzerGradlePlugin.kt to bump the internal plugin version constant

Suggested labels

IntelliJ Plugin, compiler plugin

Poem

🐰 A version bump, so clean and neat,
From 0.5.0, now 0.5.1 sweet!
wasmJs targets shine so bright,
Sealed classes fixed just right—
Release notes hop with pure delight! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The description is minimal and lacks required sections from the template (Goal, Implementation details, Explain examples). While it correctly states the PR intent, it does not follow the structured template. Expand the description to include the required sections: add Goal explaining the release purpose, Implementation details on what version changes were made, and Explain examples showing the updates. Mention running spotlessApply and apiDump.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically identifies the main purpose of the PR: preparing version 0.5.1 for release. It matches the file changes (version bumps across gradle.properties, README, CHANGELOG, and plugin code).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@skydoves skydoves merged commit 8be9e13 into main Nov 10, 2025
3 checks passed
@skydoves skydoves deleted the release/0.5.1 branch November 10, 2025 11:13
@coderabbitai coderabbitai bot mentioned this pull request Dec 6, 2025
@coderabbitai coderabbitai bot mentioned this pull request Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants