[pashidlos]

Documents how 6.0 candidates are released from the next branch, the same flow as the other SDKs. Here the tagging is manual, through JitPack.

• README "Releasing" → "Release candidates":
  • breaking changes go into next through PRs;
  • gh release create X.Y.Z-rc.N --target next --prerelease tags next and creates the pre-release, then JitPack builds it;
  • the final release merges next into master with a merge commit and tags master.
• ci.yml also runs on push to next, so a candidate is tagged on a tested commit.

No release (docs:). next already holds #122 (Java 25) and #123.

🤖 Generated with Claude Code

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (next@982296c). Learn more about missing BASE report.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##             next     #126   +/-   ##
=======================================
  Coverage        ?   91.82%           
  Complexity      ?       68           
=======================================
  Files           ?        8           
  Lines           ?      269           
  Branches        ?       22           
=======================================
  Hits            ?      247           
  Misses          ?       18           
  Partials        ?        4           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.