chore: release v0.2.1.0

[krukow]

Automated release PR for v0.2.1.0. Created by the Release workflow (run 23975149617).

[Copilot]

Pull request overview

Automated release PR to publish version 0.2.1.0, updating the documented dependency coordinates, build version, and changelog to reflect the new release.

Changes:

• Bump published version references from 0.2.1.1-SNAPSHOT to 0.2.1.0 (README + build config).
• Add a 0.2.1.0 release section in CHANGELOG.md and update compare links.
• Update README git dependency SHA to a new commit.

Show a summary per file

File	Description
README.md	Updates Maven Central version and git SHA for the release installation snippet.
CHANGELOG.md	Adds 0.2.1.0 entry and adjusts bottom compare links for the new release.
build.clj	Sets the build/publish version to 0.2.1.0.

Copilot's findings

Comments suppressed due to low confidence (1)

CHANGELOG.md:395

• The comparison links at the bottom are inconsistent with Keep a Changelog conventions and with the version ordering in this release. In particular, the [0.2.1.0] link compares v0.2.1.1-SNAPSHOT...v0.2.1.0, which suggests 0.2.1.0 is derived from a later 0.2.1.1-SNAPSHOT version. For a release section, the compare link should typically use the previous released tag as the base (e.g., v0.2.0.0...v0.2.1.0), and the snapshot compare (if kept) should start from v0.2.1.0 once the repo is bumped back to a post-release snapshot.

[Unreleased]: https://github.com/copilot-community-sdk/copilot-sdk-clojure/compare/v0.2.1.0...HEAD
[0.2.1.0]: https://github.com/copilot-community-sdk/copilot-sdk-clojure/compare/v0.2.1.1-SNAPSHOT...v0.2.1.0
[0.2.1.1-SNAPSHOT]: https://github.com/copilot-community-sdk/copilot-sdk-clojure/compare/v0.2.0.0...v0.2.1.1-SNAPSHOT

• Files reviewed: 3/3 changed files
• Comments generated: 2

[Copilot]

The changelog now lists 0.2.1.0 above 0.2.1.1-SNAPSHOT, but semver implies 0.2.1.1-SNAPSHOT is newer than 0.2.1.0. This ordering (and the fact that the repo was previously on 0.2.1.1-SNAPSHOT but is now being released as 0.2.1.0) is likely to confuse consumers and makes it unclear which section contains the full release notes for 0.2.1.0. Consider either (a) renaming/moving the existing 0.2.1.1-SNAPSHOT section into the 0.2.1.0 release notes, or (b) bumping the release version to match the snapshot line if that section represents the actual released content.

This issue also appears on line 393 of the same file.

Suggested change

	## [0.2.1.0] - 2026-04-04
	## [0.2.1.1-SNAPSHOT]

[Copilot]

This release updates the dependency version and git SHA here, but there are still docs in the repo referencing the previous 0.2.1.1-SNAPSHOT version (e.g. doc/getting-started.md). For a release PR, it would be better to update those references as well so users don’t end up copy/pasting a snapshot coordinate after 0.2.1.0 is published.