Release version 0.9.1

[lawrence-forooghian]

Summary by CodeRabbit

Release Notes

• Bug Fixes

  • Resolved a compilation error related to Xcode warning flags encountered in the previous release.

• Chores

  • Updated version to 0.9.1.

[coderabbitai]

Walkthrough

A patch version bump from 0.9.0 to 0.9.1 addressing a compilation error related to conflicting Xcode warning flags. Version string updated in the SDK and change documented in the changelog.

Changes

Cohort / File(s)	Change Summary
Version Bump 0.9.1 CHANGELOG.md, Sources/AblyChat/Version.swift	Version incremented from 0.9.0 to 0.9.1; changelog entry added documenting fix for compilation error with SDK v0.9.0 Xcode warning flags conflict

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A version hops from point-oh to point-one,
Xcode flags that clashed are now undone,
The changelog records this swift repair,
With zero-nine-point-one floating in the air! 🎉

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Release version 0.9.1" directly and clearly summarizes the main purpose of the changeset. The modifications include updating CHANGELOG.md with a 0.9.1 entry and bumping the version string in Sources/AblyChat/Version.swift from 0.9.0 to 0.9.1, which are exactly the changes expected in a release PR. The title is concise, specific, and would immediately convey to a teammate scanning the repository history that this is a release of version 0.9.1.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

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: 0

🧹 Nitpick comments (1)

CHANGELOG.md (1)

3-10: LGTM! Changelog entry is clear and properly formatted.

The 0.9.1 entry is well-positioned and clearly describes the fix. The version aligns with the update in Version.swift.

Optional: Consider wrapping the bare URL in markdown link syntax.

The static analysis tool flagged line 9 as containing a bare URL. While this is functional, wrapping it in proper markdown link syntax would be more consistent with best practices:

-**Full Changelog**: https://github.com/ably/ably-chat-swift/compare/0.9.0...0.9.1
+**Full Changelog**: [https://github.com/ably/ably-chat-swift/compare/0.9.0...0.9.1](https://github.com/ably/ably-chat-swift/compare/0.9.0...0.9.1)

This matches the format used in other changelog entries (e.g., line 108).

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 2df015d and 84eef29.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• Sources/AblyChat/Version.swift (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.swift

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.swift: Use protocol-based design; expose SDK functionality via protocols and prefer associated types with opaque return types (some Protocol) instead of existentials (any Protocol)
Isolate all mutable state to the main actor; mark stateful objects with @mainactor
Public API must use typed throws with ErrorInfo; use InternalError internally and convert at the public API boundary
For public structs emitted by the API, provide an explicit public memberwise initializer
When using AsyncSequence operators in @mainactor contexts, mark operator closures as @sendable
Task, CheckedContinuation, and AsyncThrowingStream do not support typed errors; use Result and call .get() to surface typed errors
Do not use Dictionary.mapValues for typed throws; use ablyChat_mapValuesWithTypedThrow instead
When the compiler struggles with typed throws, explicitly declare the error type on do blocks (e.g., do throws(InternalError))
Specify error types in closures using the throws(ErrorType) syntax (e.g., try items.map { jsonValue throws(InternalError) in ... })
Mark any test-only APIs with testsOnly_ prefix and wrap them in #if DEBUG

Files:

• Sources/AblyChat/Version.swift

🪛 markdownlint-cli2 (0.18.1)

CHANGELOG.md

9-9: Bare URL used

(MD034, no-bare-urls)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: Example app, iOS (Xcode 26.0)
• GitHub Check: Xcode, iOS (Xcode 26.0)
• GitHub Check: Xcode, macOS (Xcode 26.0)
• GitHub Check: Xcode, tvOS (Xcode 26.0)
• GitHub Check: Xcode, release configuration, tvOS (Xcode 26.0)
• GitHub Check: Example app, tvOS (Xcode 26.0)
• GitHub Check: Example app, macOS (Xcode 26.0)
• GitHub Check: Xcode, release configuration, macOS (Xcode 26.0)
• GitHub Check: Xcode, release configuration, iOS (Xcode 26.0)

🔇 Additional comments (1)

Sources/AblyChat/Version.swift (1)

6-6: LGTM! Version bump is correct.

The version string has been appropriately updated to 0.9.1 for this patch release. The agents property on line 9 will automatically reflect the new version through Self.version.