1.2.0 Release

[umair-ably]

Summary by CodeRabbit

• Chores

  • Version bumped to 1.2.0

• Documentation

  • Updated CHANGELOG with 1.2.0 release notes and comparison link
  • Updated README dependency/version references and release details

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e135ab9 and ac26470.

📒 Files selected for processing (3)

• CHANGELOG.md
• README.md
• Sources/AblyChat/Version.swift

---

Walkthrough

Bumps the Ably Chat SDK version from 1.1.0 to 1.2.0 in docs and internal constants; adds a changelog entry noting removal of a generic parameter from MessageSubscriptionResponseAsyncSequence. No other code or API declaration changes.

Changes

Cohort / File(s)	Summary
Changelog CHANGELOG.md	Adds 1.2.0 release entry describing removal of generic parameter from MessageSubscriptionResponseAsyncSequence and notes that subscriptions can be stored as simple properties. Includes links to full changelog and release comparison.
Docs / README README.md	Updates Swift Package Manager dependency version reference from 1.1.0 to 1.2.0.
Version Constant Sources/AblyChat/Version.swift	Updates internal ClientInformation.version constant from "1.1.0" to "1.2.0" (affects agents mapping that uses this version).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A tiny hop, the numbers climb,
One-one to one-two—what a time!
Generics trimmed, subscriptions light,
I nibble docs and dance in delight. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title '1.2.0 Release' directly matches the pull request's primary objective of releasing version 1.2.0, as evidenced by version updates across CHANGELOG.md, README.md, and Version.swift.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/1.2.0

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

CHANGELOG.md (1)

5-5: ## What's Changed should be ### What's Changed for consistency.

All other sub-headings inside release entries (e.g. ### Bug Fixes, ### What's Changed for 1.0.1) use h3 (###). Using h2 here makes 1.2.0's sub-heading visually indistinguishable from a top-level release heading.

📝 Proposed fix

-## What's Changed
+### What's Changed

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 5, Change the heading "## What's Changed" to "###
What's Changed" so it matches other sub-headings in release entries; update the
exact heading string "## What's Changed" to use three hashes ("### What's
Changed") to make the 1.2.0 sub-heading the same level as "### Bug Fixes" and
visually distinct from top-level release headings.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Line 11: The "Full Changelog" comparison URL is reversed
(compare/1.2.0...1.1.0); update the URL to follow the <older>...<newer>
convention by swapping the versions to compare/1.1.0...1.2.0 so the changelog
shows the forward diff from 1.1.0 to 1.2.0.

---

Nitpick comments:
In `@CHANGELOG.md`:
- Line 5: Change the heading "## What's Changed" to "### What's Changed" so it
matches other sub-headings in release entries; update the exact heading string
"## What's Changed" to use three hashes ("### What's Changed") to make the 1.2.0
sub-heading the same level as "### Bug Fixes" and visually distinct from
top-level release headings.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b1be2bf and e135ab9.

📒 Files selected for processing (3)

• CHANGELOG.md
• README.md
• Sources/AblyChat/Version.swift