Skip to content

release: 1.2.1 — AUTO binding by default, mocks wired out of the box - #14

Merged
maksudur03 merged 1 commit into
mainfrom
release/1.2.1
Aug 17, 2026
Merged

maksudur03 merged 1 commit into
mainfrom
release/1.2.1

Conversation

@nur-shuvo

Copy link
Copy Markdown
Collaborator

What

Numbers the changes that landed in #13 as 1.2.1 and closes the Unreleased section.

The patch number is a deliberate call, not what CHANGELOG.md's own policy computes. BindingMode.AUTO / BrowserBinding.AUTO are new constants on public enums, which breaks any host that whens 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 and docs/MIGRATION.md state the two breaking cases outright.

Version sites bumped, matching the shape of the 1.2.0 and 1.1.1 release commits:

  • SDK_VERSION in PublishingConventionPlugin.kt
  • version and DEFAULT_SDK_VERSION in the Gradle plugin
  • the plugin functional-test coordinates
  • README install snippets (Maven Central and JitPack), plus the Remote Config adapter snippet
  • docs/BUILD_VARIANTS_AND_PRODUCTION_SAFETY.md, docs/MAVEN_PUBLISHING.md
  • the three samples' versionName

One extra line: docs/MIGRATION.md pointed readers at the Unreleased heading this commit consumes, so it now points at the pre-1.0 entries instead.

Historical 1.2.0 references (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_HOME set:

  • ./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, including auto-wired coordinate resolves to the released non-snapshot version, which is the test that pins DEFAULT_SDK_VERSION to a real published coordinate

No protected-variant boundary moved, so no sample assemble/verify run was needed for this diff.

Checklist

  • Capture-path code (network/socket/push) never throws into the host app — untouched
  • No new sensitive data is captured, logged, or exported — untouched
  • Docs updated (README, both version-bearing docs, CHANGELOG, MIGRATION)
  • Scoped to one logical change

Anything reviewers should look at closely

The version number itself. 1.2.1 was chosen deliberately over the 2.0.0 the 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_VERSION now names 1.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

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>
@nur-shuvo
nur-shuvo requested a review from maksudur03 August 17, 2026 11:43
@maksudur03
maksudur03 merged commit 567fb75 into main Aug 17, 2026
1 of 2 checks passed
@maksudur03
maksudur03 deleted the release/1.2.1 branch August 17, 2026 11:45
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.

2 participants