Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release/1.2.34 #1996

Merged
merged 2 commits into from
Nov 15, 2024
Merged

Release/1.2.34 #1996

merged 2 commits into from
Nov 15, 2024

Conversation

maratal
Copy link
Collaborator

@maratal maratal commented Nov 14, 2024

Summary by CodeRabbit

Release Notes for Version 1.2.34

  • New Features

    • Introduced attachOnSubscribe option for enhanced control over channel attachment behavior.
  • Improvements

    • Updated for compatibility with Swift 6 concurrency and Xcode 16.
    • Enhanced connection state management and error handling within the ARTRealtime client.
    • Improved fallback host logic for better network resilience.
  • Documentation

    • Updated version numbers and links in the README and changelog to reflect the new version.
  • Tests

    • Expanded test coverage for connection handling, authentication mechanisms, and fallback host scenarios.

Copy link

coderabbitai bot commented Nov 14, 2024

Walkthrough

The pull request introduces several updates across multiple files, primarily focusing on version increments from 1.2.33 to 1.2.34. Key changes include the addition of the attachOnSubscribe option in ARTRealtimeChannelOptions, preparation for Swift 6 concurrency, and compatibility with Xcode 16. The CHANGELOG.md has been updated to reflect these changes, and various test files have been modified to align with the new version, ensuring that the library's functionality and error handling are robust under different conditions.

Changes

File Change Summary
CHANGELOG.md Updated for version 1.2.34, including attachOnSubscribe in ARTRealtimeChannelOptions and Swift 6 concurrency prep.
README.md Version number updated from 1.2.33 to 1.2.34 in installation instructions and release links.
Scripts/jazzy.sh Module version updated from 1.2.33 to 1.2.34 in the --module-version flag.
Source/ARTClientInformation.m Library version constant updated from "1.2.33" to "1.2.34".
Test/Tests/ARTDefaultTests.swift Updated testVersions to reflect expected library version change to 1.2.34.
Test/Tests/ClientInformationTests.swift Updated expected agent version string from 1.2.33 to 1.2.34 in multiple test cases.
Test/Tests/RealtimeClientConnectionTests.swift Enhanced tests for connection state management, error handling, and fallback logic; updated expected version in tests.
Test/Tests/RestClientTests.swift Updated expected version in tests; enhanced tests for fallback hosts and authentication mechanisms.
Version.xcconfig Project version updated from 1.2.33 to 1.2.34.

Possibly related PRs

Suggested reviewers

  • umair-ably
  • lawrence-forooghian

🐇 In the meadow, we hop and play,
With version numbers bright as day.
From 1.2.33 to 1.2.34,
New features added, oh what a score!
Attach on subscribe, we cheer with glee,
For Swift and Xcode, as happy as can be! 🌼

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 SwiftLint
Test/Tests/RealtimeClientConnectionTests.swift
Test/Tests/RestClientTests.swift

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)
CHANGELOG.md (1)

7-11: Consider adding more details about the changes

While the changes are clearly listed, it would be helpful to add more context about:

  • The impact of Swift 6 concurrency preparation
  • What the new attachOnSubscribe option does and when to use it
  • The specific Xcode 16 compatibility improvements
🧰 Tools
🪛 Markdownlint

9-9: null
Bare URL used

(MD034, no-bare-urls)


9-9: null
Bare URL used

(MD034, no-bare-urls)


10-10: null
Bare URL used

(MD034, no-bare-urls)


11-11: null
Bare URL used

(MD034, no-bare-urls)

Test/Tests/RealtimeClientConnectionTests.swift (1)

387-387: Consider using a constant for the agent version to avoid hardcoding

Currently, the agent version "ably-cocoa/1.2.34" is hardcoded in the test. To improve maintainability and reduce the risk of errors when updating the version in the future, consider defining a constant for the agent version.

Apply this diff to replace the hardcoded string:

- expect(query).to(haveParam("agent", hasPrefix: "ably-cocoa/1.2.34"))
+ expect(query).to(haveParam("agent", hasPrefix: agentVersion))

Outside the selected line range, define the constant agentVersion at an appropriate location, such as at the top of the test file:

let agentVersion = "ably-cocoa/1.2.34"
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f7bff4b and 3ae52f9.

📒 Files selected for processing (9)
  • CHANGELOG.md (1 hunks)
  • README.md (2 hunks)
  • Scripts/jazzy.sh (1 hunks)
  • Source/ARTClientInformation.m (1 hunks)
  • Test/Tests/ARTDefaultTests.swift (1 hunks)
  • Test/Tests/ClientInformationTests.swift (3 hunks)
  • Test/Tests/RealtimeClientConnectionTests.swift (1 hunks)
  • Test/Tests/RestClientTests.swift (1 hunks)
  • Version.xcconfig (1 hunks)
✅ Files skipped from review due to trivial changes (4)
  • README.md
  • Scripts/jazzy.sh
  • Source/ARTClientInformation.m
  • Version.xcconfig
🧰 Additional context used
🪛 Markdownlint
CHANGELOG.md

5-5: null
Bare URL used

(MD034, no-bare-urls)


9-9: null
Bare URL used

(MD034, no-bare-urls)


9-9: null
Bare URL used

(MD034, no-bare-urls)


10-10: null
Bare URL used

(MD034, no-bare-urls)


11-11: null
Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (7)
Test/Tests/ARTDefaultTests.swift (1)

9-9: LGTM! Version update looks correct.

The test has been properly updated to expect the new version "1.2.34", which aligns with the release version.

Let's verify version consistency across all relevant files:

✅ Verification successful

Version consistency verified across key files

The version "1.2.34" is consistently set across all critical locations:

  • Source/ARTClientInformation.m: Library version constant
  • Test/Tests/ARTDefaultTests.swift: Test assertion
  • CHANGELOG.md: Release entry
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across the codebase
# Expected version: 1.2.34

echo "Checking version numbers across key files..."

# Check Version.xcconfig
rg -l "MARKETING_VERSION = 1\.2\.34" --type-add 'xcconfig:*.xcconfig' --type xcconfig

# Check Source files
rg "libraryVersion.*1\.2\.34" --type swift --type objc

# Check Documentation
rg "version.*1\.2\.34" README.md
rg "## \[1\.2\.34\]" CHANGELOG.md

echo "Any mismatches in the above files would indicate inconsistent versioning"

Length of output: 719

Test/Tests/ClientInformationTests.swift (4)

12-12: LGTM: Version update is consistent with release.

The version string update in the test assertion correctly reflects the new version 1.2.34.


30-30: LGTM: Version update is consistent with release.

The version string update in the agent identifier test correctly reflects the new version 1.2.34.


45-45: LGTM: Version update is consistent with release.

The version string update in the complex agent identifier test correctly reflects the new version 1.2.34.


12-12: Verify version consistency across the codebase.

Let's ensure the version number is consistently updated across all relevant files.

Also applies to: 30-30, 45-45

✅ Verification successful

Let me run one more verification to check for version strings in test files and any potential configuration files:


Version 1.2.34 is consistently used across the codebase

The version has been properly updated in all relevant locations:

  • Source code: ARTClientInformation.m
  • Documentation: README.md
  • Changelog: CHANGELOG.md
  • Test files: All test assertions use the new version 1.2.34
  • No occurrences of old version 1.2.33 found except in changelog history
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any remaining occurrences of the old version and verify new version is consistently used

echo "Checking for old version 1.2.33..."
rg "1\.2\.33" --type-not git

echo -e "\nVerifying new version 1.2.34 in key files..."
rg "1\.2\.34" CHANGELOG.md Source/ARTClientInformation.m README.md

Length of output: 895


Script:

#!/bin/bash
# Check test files and configuration files for version strings
echo "Checking test files for version strings..."
rg "1\.2\.3[0-9]" "Test/" -l

echo -e "\nChecking any potential configuration or build files..."
fd "\.podspec|\.plist|\.xcconfig|\.swift|\.m|\.h" --type f --exec rg "1\.2\.3[0-9]" {} \;

Length of output: 1936

CHANGELOG.md (1)

3-5: LGTM: Version header follows standard format

The version header follows the standard format with:

  • Version number as a link to the tag
  • Full changelog comparison link
🧰 Tools
🪛 Markdownlint

5-5: null
Bare URL used

(MD034, no-bare-urls)

Test/Tests/RestClientTests.swift (1)

1739-1739: LGTM!

The test assertion correctly verifies the updated version number in the Ably-Agent header.

@maratal maratal merged commit a241afa into main Nov 15, 2024
8 checks passed
@maratal maratal deleted the release/1.2.34 branch November 15, 2024 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants