Skip to content

Bump Gradle 9.9.1, kotlinx-serialization 1.13.0, kotlin-logging 8.0.7 - #75

Merged
pambrose merged 1 commit into
masterfrom
bump-gradle-serialization-logging
Nov 13, 2026
Merged

pambrose merged 1 commit into
masterfrom
bump-gradle-serialization-logging

Conversation

@pambrose

Copy link
Copy Markdown
Member

Summary

  • Gradle 9.9.0 → 9.9.1 (catalog gradle-wrapper entry and gradle-wrapper.properties together). make upgrade-wrapper at 9.9.1 leaves gradle-wrapper.jar, gradlew, and gradlew.bat unchanged.
  • kotlinx-serialization 1.12.0 → 1.13.0
  • kotlin-logging 8.0.6 → 8.0.7

Notes update

kotlinx-serialization 1.13.0 reverts 1.12.0's wrapping of serializer exceptions in JsonEncodingException / JsonDecodingException. Because vapi4k-utils exports it as an api dependency, the Unreleased notes had warned consumers about that wrapping. Measured from 1.8.2, which shipped 1.11.0, there is now no change, so:

  • CHANGELOG.md: the 1.12 wrapping bullet is removed, and the provider-serializer bullet no longer cites it. Versions updated.
  • RELEASE_NOTES.md: Upgrading from 1.8.2 keeps only the provider-serializer change. The dependency line explains the 1.12/1.13 round trip. Versions updated.
  • ProviderSerializerErrorTest KDoc updated. The tests pin SerializationException, which passes through on both versions.

The provider serializers still throw SerializationException rather than IllegalStateException. That remains a visible change for consumers and is still documented.

🤖 Generated with Claude Code

- Gradle 9.9.0 -> 9.9.1 (catalog entry and wrapper properties; regenerating
  the wrapper at 9.9.1 left gradle-wrapper.jar and the scripts unchanged)
- kotlinx-serialization 1.12.0 -> 1.13.0
- kotlin-logging 8.0.6 -> 8.0.7

kotlinx-serialization 1.13.0 reverts 1.12.0's wrapping of serializer
exceptions in JsonEncodingException / JsonDecodingException. vapi4k-utils
exports it as an api dependency, so the Unreleased notes no longer warn
consumers about the wrapping: measured from 1.8.2 (1.11.0), there is no
change. The provider serializers still throw SerializationException, which
stays a change for code catching IllegalStateException. The KDoc on
ProviderSerializerErrorTest is updated to match.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

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.

@pambrose
pambrose merged commit f278dce into master Nov 13, 2026
10 checks passed
@pambrose
pambrose deleted the bump-gradle-serialization-logging branch November 13, 2026 18:44
@codecov

codecov Bot commented Nov 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

pambrose added a commit that referenced this pull request Nov 13, 2026
#71 switched the model, voice, transcriber and transfer-destination
serializers to throw SerializationException for an unregistered DTO class,
because kotlinx-serialization 1.12 wrapped any other exception in
JsonEncodingException. kotlinx-serialization 1.13.0 (#75) reverted that
wrapping, so the switch is no longer needed and would only be a behavior
change for consumers catching IllegalStateException.

- Serializers use error("Invalid <kind> provider: ...") again; the four
  files match their pre-#71 contents
- ModelSerializerTest and ProviderSerializerErrorTest assert exactly
  IllegalStateException with the same message, which also guards against
  kotlinx-serialization reintroducing the wrapping
- CHANGELOG / RELEASE_NOTES: drop the serializer entry and the now-empty
  "Upgrading from 1.8.2" section
- llms.txt: Kotlinx Serialization 1.13.0

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant