Skip to content

chore(android): release the Kotlin SDK 0.7.0 - #2072

Merged
aleksandar-apostolov merged 1 commit into
mainfrom
release-kotlin-0.7.0
Nov 18, 2026
Merged

aleksandar-apostolov merged 1 commit into
mainfrom
release-kotlin-0.7.0

Conversation

@aleksandar-apostolov

Copy link
Copy Markdown
Contributor

Closes AND-1971

Why

Ships to Kotlin what merged since 0.5.0: live generative UI (#2054), session tools (#2050), session filters (#2001), regenerate and edit with branches (#1983), rewind (#2012), and tool_timeout_ms on fork and resume (#2004, #2046). 0.7.0 matches the repo release; Dart's stream_agents shipped 0.7.0 in #2052.

Conversation is no longer a data class, so Java loses its no-argument constructor (see CHANGELOG).

Changes

  • sdks/kotlin/gradle.properties: version=0.7.0.

Merging this publishes io.getstream:stream-agents-android-core:0.7.0 to https://stream-io-repo.com and tags the commit sdk-kotlin-v0.7.0. It is the first Kotlin release from main (#2062).

Validation

  • The Check the version job on this pull request: the branch matches version, and 0.7.0 is newer than sdk-kotlin-v0.5.0 and not yet published.

@coderabbitai

coderabbitai Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The Kotlin SDK Gradle version changes from 0.5.0 to 0.7.0.

Merge Risk: Minimal · up to ecb40

This release bumps the Kotlin SDK version to 0.7.0. No actionable merge risk was found. Note that the Conversation class change affects Java callers, as the description already states.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Recent review info

Run configuration

Commits

Reviewing files that changed from the base of the PR and between c37de15 and ecb4082.

Files selected for processing: 1

  • sdks/kotlin/gradle.properties

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

@aleksandar-apostolov
aleksandar-apostolov merged commit e2f68ff into main Nov 18, 2026
25 checks passed
@aleksandar-apostolov
aleksandar-apostolov deleted the release-kotlin-0.7.0 branch November 18, 2026 13:13
kanat added a commit that referenced this pull request Nov 19, 2026
## Why

`publish-sdk-kotlin.yml` published on any push to `main` whose
`gradle.properties` held a new non-SNAPSHOT version, so a refactor PR
that bumped the version published a release (AI-3368). The release flow
stays as it is: the merge of a PR from `release-kotlin-X.Y.Z` publishes
and tags.

## How it works

```
push to main
 └─ gh api commits/$GITHUB_SHA/pulls -> merged PRs into main
     ├─ head = release-kotlin-X.Y.Z -> existing checks (version == branch, newer, unpublished) -> releases + tag
     └─ anything else (direct push, other PR) -> ::notice + channel=none
```

`e2f68ff28` (#2072, the 0.7.0 release) is still associated with its PR
through the API: head `release-kotlin-0.7.0`, base `main`, merged.

## Changes

- `version` job: `pull-requests: read` (this job only), `GH_TOKEN`, and
the PR lookup before the version checks. The old "main with a SNAPSHOT
or already-tagged version" branch is gone: every non-release push exits
earlier.
- Workflow header and `sdks/kotlin/README.md` say the same, and say how
to recover a release merge whose run says nothing is published: re-run
all its jobs (the PR lookup can lag right after the merge). Reasoned
from the step, not run live.
- Behaviour change: a release merge whose version is already tagged now
fails `already released` (red, nothing published) instead of ending
green with `none`.
- Closes the comment part of AI-3364: the two `environment: release`
comments name the secrets as GetStream organization secrets that the
environment does not limit. The `environment: release` lines are
unchanged; AI-3372 tracks limiting the secrets to the release jobs.

## Validation

No local workflow run exists, so the step's own `run:` block is
extracted from the YAML and run with `gh` (real `--jq` filter over a
fixture) and `curl` stubbed. `actionlint` is clean.

| Case (push to main unless noted) | Base | Head |
|---|---|---|
| PR head `release-kotlin-0.8.0`, version 0.8.0 | releases | releases |
| PR head `feature/refactor`, version 0.8.0 | **releases** | none |
| no PR (direct push) | **releases** | none |
| release PR not merged / base not `main` / head `release-kotlin-0.8.0x`
/ SNAPSHOT head | n/a | none |
| head `release-kotlin-0.9.0`, version 0.8.0 | releases | error
(mismatch) |
| pull_request event, release branch | releases | releases |

Mutations (drop the gate, drop `merged_at`, drop `base == main`,
unanchor or loosen the branch regex, drop `exit 0` after none, drop `||
true`, wrong event, keep BRANCH): all 9 killed by the case table.

Unverified: the real workflow on GitHub (the API can lag right after a
merge: the lookup then gives none and publishes nothing; unverified),
and that the `pull-requests: read` job permission is enough for
`commits/{sha}/pulls` (documented so; not run).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Sonnet 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.

2 participants