Repository navigation
Release 1.3.0 - #29
Merged
Merged
Conversation
Bumps SDK_VERSION, the Gradle plugin version, DEFAULT_SDK_VERSION, the sample versionNames, and every consumer-facing coordinate in the docs from 1.2.4 to 1.3.0, and closes out the CHANGELOG's Unreleased section. A minor, not a major: the release adds public API (InspectorDataSource .clearTransactions(), InspectorAction.ClearTransactions, and DELETE /api/v1/network/transactions), which the versioning policy says requires a minor. NetworkTransactionStore's new abstract clear() is source-breaking for an external implementor, but it sits in sdk:network rather than sdk:api, and the policy reserves a major for breaks to sdk:api. The CHANGELOG left this number open for the release decision; it now records the reasoning. The FileProvider note in docs/FAQ_TROUBLESHOOTING.md keeps its 1.2.4/1.2.3 spellings -- it is a historical statement about when that fix landed, not a pointer at the current release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Shakibuzzaman3104
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Cuts 1.3.0. Bumps
SDK_VERSION, the Gradle pluginversion,DEFAULT_SDK_VERSION, the threesample
versionNames, and every consumer-facing coordinate in the docs from 1.2.4, then closes outthe CHANGELOG's
Unreleasedsection.Why a minor, not a major. The CHANGELOG deliberately left this number open ("left for the
release decision rather than assumed"). The release adds public API —
InspectorDataSource .clearTransactions(),InspectorAction.ClearTransactions, andDELETE /api/v1/network/transactions— which the versioning policy says
requires a minor.
NetworkTransactionStore's new abstractclear()is source-breaking for anexternal implementor, but it sits in
sdk:network, notsdk:api, and the policy reserves a majorfor breaks to
sdk:api. The CHANGELOG now records that reasoning in place of the open question.One deliberate non-change: the FileProvider entry in
docs/FAQ_TROUBLESHOOTING.mdkeeps its1.2.4/1.2.3spellings. That paragraph is a historical statement about when the fix landed, not apointer at the current release, so bumping it would have made it wrong.
Verification
Run with
ANDROID_HOMEset (the plugin's functional testserror()out without it)../gradlew testDebugUnitTest— passing./gradlew -p gradle-plugin test— 32/32 passing (this is the suite the bump actually touches)./gradlew apiCheck— clean; no API change in this diff, so noapiDumpneeded./gradlew publishToMavenLocal— passing; all 34 artifacts resolve at 1.3.0, POM version confirmed./gradlew ktlintCheck detekt— fails, but identically onmain(verified by re-running onmain): 3 detekt findings and 2 ktlint findings insamples/compose-app/MainActivity.kt,samples/foundation-app/MainActivity.kt, andsdk/server-api/LocalServerEngine.kt— all sourcefiles this diff does not touch, all from 69d3414. Left alone to keep this PR to one logical
change; they want their own fix before the tag goes out.
Not run: sample assemble/verify — this diff touches no debug/release or protected-variant boundary.
Checklist
docs/, andsdk/storage-room/README.mdAnything reviewers should look at closely
The version number itself — 1.3.0 over 2.0.0 — is the one real judgment call here, and the
NetworkTransactionStore.clear()reasoning above is where to push back if you read that break asmajor-worthy.
Worth deciding separately: the pre-existing lint failures on
mainmean CI is red on this branchthrough no fault of the diff, and the release checklist wants a green build before the tag.