Skip to content

fix(codegen): complete follow-up fixes for #418#419

Merged
wax911 merged 2 commits into
developfrom
fix/codegen-followups-418
Jun 24, 2026
Merged

fix(codegen): complete follow-up fixes for #418#419
wax911 merged 2 commits into
developfrom
fix/codegen-followups-418

Conversation

@wax911

@wax911 wax911 commented Jun 24, 2026

Copy link
Copy Markdown
Member

Pull Request Template

Thank you for contributing! Please take a moment to review our contributing guidelines
to make the process easy and effective for everyone involved.

Please open an issue before embarking on any significant pull request, especially those that
add a new library or change existing tests, otherwise you risk spending a lot of time working
on something that might not end up being merged into the project.

Before opening a pull request, please ensure:

  • You have followed our contributing guidelines
  • Double-check your branch is based on develop and targets develop (where applicable)
  • Pull request has tests (If applicable)
  • Code is well-commented, linted and follows project conventions
  • Documentation is updated (if necessary)
  • Description explains the issue/use-case resolved

Description

Fixes and follow-ups for #418.

This PR completes the #418 stream with focused runtime, plugin, publishing, and documentation updates:

  • Runtime converter updates to support registry-only converter API usage paths.
  • Gradle plugin wiring and functional coverage for compile, KSP, KAPT, and multi-target configurations.
  • Standalone gradle-plugin local publishing flow plus published-consumer verification against mavenLocal.
  • Delivery/build-context updates via .jitpack.yml, README, MIGRATION, AGENTS, and build dependency reference docs.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Enhancement (Improve existing functionality)

IMPORTANT: By submitting a patch, you agree to allow the project
owners to license your work under the terms of the Apache License.

@github-actions github-actions Bot added the docs label Jun 24, 2026
@codacy-production

codacy-production Bot commented Jun 24, 2026

Copy link
Copy Markdown

Not up to standards ⛔

🔴 Issues 13 medium · 16 minor

Alerts:
⚠ 29 issues (≤ 0 issues of at least minor severity)

Results:
29 new issues

Category Results
Documentation 16 minor
Complexity 13 medium

View in Codacy

🟢 Metrics 65 complexity · 2 duplication

Metric Results
Complexity 65
Duplication 2

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@wax911 wax911 force-pushed the fix/codegen-followups-418 branch from f732ee1 to c74bbdc Compare June 24, 2026 15:05

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved automated PR

@wax911 wax911 force-pushed the fix/codegen-followups-418 branch from ff0a410 to e83e151 Compare June 24, 2026 16:50
@wax911 wax911 added bug fix and removed docs labels Jun 24, 2026
@wax911 wax911 merged commit 0aed236 into develop Jun 24, 2026
10 of 11 checks passed
@wax911 wax911 deleted the fix/codegen-followups-418 branch June 24, 2026 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Codegen follow-ups: plugin publishing, generated source task wiring, and registry-only converter API

1 participant