Repository navigation
release: 1.2.1 — AUTO binding by default, mocks wired out of the box - #14
Merged
Merged
Conversation
Numbers the changes that landed in #13. Patch is a deliberate call rather than what the changelog's own policy computes: `BindingMode.AUTO` / `BrowserBinding.AUTO` are new enum constants, which breaks any host that `when`s over them exhaustively, and the default binding moving off loopback is a behavioural change to a security default. Both read as major. Nothing was removed and no signature changed, so the upgrade is a no-op for hosts doing neither; the changelog and MIGRATION.md say so plainly instead of letting the version number imply it. Bumps SDK_VERSION, the Gradle plugin version and its DEFAULT_SDK_VERSION, the plugin functional-test coordinates, README install snippets, both version-bearing docs, and the three samples' versionName. Also repoints MIGRATION.md's pre-1.0 pointer, which referenced the Unreleased heading this commit consumes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
maksudur03
approved these changes
Aug 17, 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
Numbers the changes that landed in #13 as 1.2.1 and closes the
Unreleasedsection.The patch number is a deliberate call, not what CHANGELOG.md's own policy computes.
BindingMode.AUTO/BrowserBinding.AUTOare new constants on public enums, which breaks any host thatwhens over them exhaustively, and the default binding moving off loopback is a behavioural change to a security default — both read as major. Nothing was removed and no signature changed, so the upgrade is a no-op for hosts doing neither. Rather than let the version number imply more compatibility than there is, the changelog's version note anddocs/MIGRATION.mdstate the two breaking cases outright.Version sites bumped, matching the shape of the 1.2.0 and 1.1.1 release commits:
SDK_VERSIONinPublishingConventionPlugin.ktversionandDEFAULT_SDK_VERSIONin the Gradle plugindocs/BUILD_VARIANTS_AND_PRODUCTION_SAFETY.md,docs/MAVEN_PUBLISHING.mdversionNameOne extra line:
docs/MIGRATION.mdpointed readers at the Unreleased heading this commit consumes, so it now points at the pre-1.0 entries instead.Historical
1.2.0references (the "these artifacts first ship in 1.2.0" note,## Upgrading from 1.2.0, "to keep 1.2.0 behaviour") are left alone — they name a specific past release, not the current one.Verification
Run locally with
ANDROID_HOMEset:./gradlew testDebugUnitTest— passing./gradlew ktlintCheck detekt— clean, no new findings./gradlew apiCheck— clean; no API changed in this diff./gradlew :gradle-plugin:test— 29/29 passing, includingauto-wired coordinate resolves to the released non-snapshot version, which is the test that pinsDEFAULT_SDK_VERSIONto a real published coordinateNo protected-variant boundary moved, so no sample assemble/verify run was needed for this diff.
Checklist
Anything reviewers should look at closely
The version number itself.
1.2.1was chosen deliberately over the2.0.0the changelog argued for; if you disagree, this is the commit to say so on — after the tag and the Central publish it is much more expensive to revisit.Security-adjacent, stated plainly: this release ships a loosened default. The server now binds a real network interface out of the box and the dashboard speaks plaintext HTTP, so on an untrusted network headers, tokens, and bodies are readable by anyone on it. That change landed in #13; this PR only puts a number on it.
DEFAULT_SDK_VERSIONnow names1.2.1, which is not on Maven Central until this release publishes — the same ordering the 1.2.0 and 1.1.1 release commits used.🤖 Generated with Claude Code