release: 2.0.0

[cjbell]

The v2.0.0 release publish (run) failed Maven Central validation with "component ... @1.0.0 already exists". The tag points at 1925443, where build.gradle.kts still says version = "1.0.0". This repo has no release-please workflow; the 1.0.0 bump came from the Stainless bot's release PR (#36). So nothing bumped the version before the release was created, and the job rebuilt 1.0.0.

This PR is the release PR that was missing:

• release: 2.0.0 bumps .release-please-manifest.json, build.gradle.kts, and the README install and badge snippets to 2.0.0. It also adds the 2.0.0 CHANGELOG entry covering #40 and #41.
• Publish guard: on release events, the publish workflow now fails in its first step if the tag doesn't match the x-release-please-version in build.gradle.kts. This case then shows a clear error instead of a Central validation failure after a full build and upload.

The failed run did get through the build, signing, and upload steps, so the new publishing setup from #41 works; only the version was wrong.

After merging

The existing v2.0.0 tag points at the pre-bump commit, so:

1. Delete the v2.0.0 GitHub release and the v2.0.0 tag.
2. Create the v2.0.0 release again, targeting the merge commit of this PR. That triggers the publish workflow.
3. Optionally, drop the failed deployment b1bb6abf-c8a1-449c-9f87-61ad08a5e831 in the Central Portal. It failed validation, so nothing was published.

  

[cursor]

Approved: this is an auto-release PR and required CI (lint, test) is green. The PR is already merged, so no further merge action is needed.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}