Skip to content

chore(release): prepare Java SDK 0.1.0 - #4

Merged
moonyue-w merged 2 commits into
mainfrom
codex/java-release-0.1.0
Oct 21, 2026
Merged

moonyue-w merged 2 commits into
mainfrom
codex/java-release-0.1.0

Conversation

@moonyue-w

Copy link
Copy Markdown
Contributor

Change

Prepare com.qoder.sdk:qoder-cloud-agents-sdk:0.1.0 from the published RC without changes to SDK implementation, test sources or publishing workflows. Update both POMs and the changelog, correct stale unpublished-package descriptions, and document direct Maven consumption and RC promotion.

Organize the README around the existing Go SDK documentation style: capability overview, installation, PAT/SA authentication, regions, Session SSE, async cancellation, pagination, retries/errors and resource guides. Keep detailed client settings in docs/client-configuration.md. Clarify that Managed APIs are planned for a future release and absent only from the current Java version. Go, Python and TypeScript are unchanged.

Validation

  • make quality passes on JDK 17: formatting, version/changelog, 115 local documentation links and 38 maintenance-script tests.
  • All 6 README Java snippets compile against the packaged SDK on both JDK 8 and JDK 17; this is compilation validation, not a live execution run.
  • make test passes on JDK 8 and JDK 17: 545 SDK tests, 62 independent packaged-consumer tests, sources/Javadoc and Java 8 package checks per runtime.
  • Implementation, SDK/example test sources and .github/ match v0.1.0-rc.1 exactly.
  • Prior published-RC acceptance: 3,040 offline checks across Java 8/11/17/21/25 passed; live CN/Global PAT/SA first run passed 184/190 groups, and all six failed cases passed one targeted retry. These are RC results, not post-publication verification of 0.1.0. The original failures and scope limits are documented in the maintenance guide.
  • External Channel/QR/Pairing flows, audio-device quality, long-duration stability and production fault injection were not exercised live.

The 0.1.0 version has not been published by this change. After merge, require CI on the merged main SHA and run the release workflow with a new batch ID. Keep the existing RC tag, deployment and artifact immutable.

@moonyue-w
moonyue-w merged commit 1c19623 into main Oct 21, 2026
12 checks passed
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