Release version 0.3.0

[lawrence-forooghian]

Currently failing due to the dependency bump; requires ably-cocoa 1.2.54 (see comment on ably/ably-cocoa#2160)

Ready to go now

Summary by CodeRabbit

• Chores
  • Released version 0.3.0 with internal improvements and no public API changes
  • Updated Ably package dependency declarations to use flexible version requirements (now referencing specific published versions)
• Documentation
  • Added 0.3.0 changelog section and clarified prior 0.2.0 entries (build fix and JSON number handling)

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated changelog with a new 0.3.0 section and edits to 0.2.0; switched two Swift Package Manager dependencies from revision-pinned to semantic version constraints and updated corresponding resolved lock files.

Changes

Cohort / File(s)	Summary
Changelog CHANGELOG.md	Added a new 0.3.0 section ("No public API changes") with three internal-improvement bullets and Full Changelog link; added two fix bullets under 0.2.0 describing SPM dependency spec and JSONValue.number type change.
Package manifest Package.swift	Replaced revision-pinned dependencies with version-based constraints: ably-cocoa → from: "1.2.55", ably-cocoa-plugin-support → from: "1.0.0"; removed inline comment guidance.
Resolved lockfiles AblyLiveObjects.xcworkspace/xcshareddata/swiftpm/Package.resolved, Package.resolved	Updated pins: ably-cocoa revision → new revision and added version 1.2.55; ably-cocoa-plugin-support revision → new revision and added version 1.0.0; originHash values updated.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Pay attention to: updated versions in Package.swift, consistency with both Package.resolved files, and accuracy of changelog bullet wording.

Poem

🐰 Hopped through files with gentle paws,
Unpinned the pins and fixed the laws,
Changelog trimmed and versions set,
A tidy patch — no hair to fret! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Release version 0.3.0' directly aligns with the main objective of the PR—releasing version 0.3.0. The changes include CHANGELOG updates documenting the 0.3.0 release and dependency version updates to support this release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ 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.3.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: 2

🧹 Nitpick comments (1)

CHANGELOG.md (1)

13-13: Consider wrapping URLs in angle brackets (optional).

The markdown linter flags the bare URL. For consistency, you could wrap all changelog URLs in angle brackets (<URL>) or convert them to proper markdown links. However, this is consistent with the existing style in the file (see line 22).

📜 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 ed21c46 and ef2cf3b.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• Package.swift (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.swift

📄 CodeRabbit inference engine (.cursor/rules/swift.mdc)

**/*.swift: Specify an explicit access control level (SwiftLint explicit_acl) for all declarations in Swift code (tests are exempt)
When extending a type, put the access level on the extension declaration rather than on each member (tests are exempt)
Prefer implicit .init(...) when the type can be inferred in initializer expressions
Prefer enum case shorthand (.caseName) when the type can be inferred
For JSONValue or WireValue, prefer using literal syntax via ExpressibleBy*Literal where possible
Prefer Swift raw string literals for JSON strings instead of escaping double quotes
When an array literal begins with an initializer expression, place the initializer on the line after the opening bracket

Files:

• Package.swift

🪛 markdownlint-cli2 (0.18.1)

CHANGELOG.md

13-13: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (1)

CHANGELOG.md (1)

3-14: LGTM! Changelog entry is well-structured.

The 0.3.0 changelog entry properly documents the internal improvements with no public API changes, and follows the same format as existing entries.