ci: add prerelease workflow

[kikin81]

Description

Changes

• ci: add prerelease workflow

🚀 PR created with fotingo

[github-actions]

Release notes preview

Below is a preview of the release notes if your PR gets merged.

---

2.0.0 (2025-12-11)

⚠ BREAKING CHANGES

• deps: kotlin 2.1.20

Build System

• adds sdkman file (7e80474)

Miscellaneous

• add detekt for code quality (d49f5cc)
• add detekt to .pre-commit-config.yaml (91eb6a4)
• add sec scan: add sec scan (e7b6079)
• move detekt to a config/detekt folder (94be28c)
• remove unused imports (95384a0)
• rename tests module (2874b81)
• deps: update actions/checkout action to v5 (43625af)
• update AGP to 8.11.1 (bbb1f9b)
• deps: update all ci non-major dependencies (a8969bc)
• update CODEOWNERS (e786dc8)
• update compose-bom 2025.07.00 (4093828)
• update gradle to 8.5 (9b8c58b)
• deps: update gradle to v8.14.3 (5c18b74)
• gradle: update Gradle wrapper to 8.13 (8f435ce)
• update gson 2.13.1 (e4f9da6)
• update links to materials (fd3e053)
• Update links to materials (38153eb)
• deps: update pre-commit hook pre-commit/pre-commit-hooks to v6 (72d84b9)
• update readme (5cd797b)

Continuous Integration

• add detekt job to ci.yaml (2b97b82)
• add prerelease workflow (21f7cf1)
• adds build step to our ci (f9c7b40)
• release: adds release github workflow and documentation (cb235f9), closes #11
• renovate: adds renovate bot configuration for jvm project (7173470), closes #9
• changes to detekt job (f2fda69)
• fix ci job failure (46c589f)
• fix detekt job, updates detekt to latest version (eb44767)
• remove detekt job - as its part of the lint job (271f5a0)
• update tests to use open-turo jvm tests (538942f)
• use open-turo jvm actions for testing (8ac7be2)
• use test/v2 (bb4a5ff)
• use the open-turo github token for release (779f7b5)

Documentation

• add breaking changes documentation for v2 (3617e3e)
• add detekt.md (f79429b)

Features

• allow sealed classes as navigation arguments (692fc74)
• deps: update androidx libs and target sdk to 35 (ecf9485)
• deps: update autoService and autoServiceKsp (a27fbab)
• deps: update kotlin, dagger and ksp (70e3adf)

Bug Fixes

• fix CI test workflow (9aeb108)
• fixes build for missing method (abe99f3)
• specify correct gradle task for Android tests (e46ea20)
• deps: update dependency io.kotest:kotest-assertions-core to v6 (35a2911)

Styles

• add TrailingCommaOnCallSite and TrailingCommaOnDeclarationSite in rules (f86563c)
• detekt fixes to existing files (4562704)
• detekt fixes to existing files (11a3101)
• enable TooManyFunctions and LongMethod rules for detekt (7a1654b)
• remove detekt-formatting-1.23.0.jar (b717dda)

[github-actions]

---

Breaking changes file docs/breaking-changes/v2.md

Breaking changes in v2

Description of changes

This release includes a major update to Kotlin version 2.1.20, which introduces breaking changes that may affect existing codebases. The update also includes updates to Dagger and KSP dependencies to maintain compatibility with the new Kotlin version.

Key Changes

• Kotlin version upgrade: Updated from previous version to Kotlin 2.1.20
• Dagger dependency update: Updated Dagger to maintain compatibility with Kotlin 2.1.20
• KSP dependency update: Updated KSP to maintain compatibility with Kotlin 2.1.20

Upgrade instructions

Prerequisites

• Ensure your project is compatible with Kotlin 2.1.20
• Review any custom KSP processors or annotation processors for compatibility
• Check Dagger-related code for any deprecated APIs or breaking changes

Required Steps

1. Update your project's Kotlin version to 2.1.20
2. Update Dagger dependencies to the latest compatible version
3. Update KSP dependencies to the latest compatible version
4. Review and update any custom annotation processors if applicable

Code Examples

If you have custom KSP processors, ensure they implement the latest KSP APIs:

// Update your KSP processor implementations to use the latest APIs
// Check the official KSP documentation for migration guides

Testing

After upgrading:

1. Run your full test suite to identify any breaking changes
2. Test annotation processing and code generation
3. Verify that all Dagger-related functionality works as expected
4. Check that any custom KSP processors continue to function correctly

Rollback Plan

If you encounter issues, you can temporarily rollback to the previous version while investigating compatibility issues. However, it's recommended to address the breaking changes rather than staying on older versions.

---