Skip to content

Conversation

@tiginamaria
Copy link
Collaborator

Motivation and Context

Breaking Changes


Type of the changes

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tests improvement
  • Refactoring
  • CI/CD changes
  • Dependencies update

Checklist

  • The pull request has a description of the proposed change
  • I read the Contributing Guidelines before opening the pull request
  • The pull request uses develop as the base branch
  • Tests for the changes have been added
  • All new and existing tests passed
Additional steps for pull requests adding a new feature
  • An issue describing the proposed change exists
  • The pull request includes a link to the issue
  • The change was discussed and approved in the issue
  • Docs have been added / updated

@tiginamaria tiginamaria merged commit b4b671c into 0.6.1 Jan 28, 2026
13 checks passed
@tiginamaria tiginamaria deleted the tigina/0.6.1 branch January 28, 2026 14:46
@github-actions
Copy link

Qodana for JVM

1277 new problems were found

Inspection name Severity Problems
Check Kotlin and Java source code coverage 🔶 Warning 1257
Missing KDoc for public API declaration 🔶 Warning 20
@@ Code coverage @@
+ 71% total lines covered
18806 lines analyzed, 13411 lines covered
# Calculated according to the filters of your coverage tool

☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

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