Release/1.0.7

[sacOO7]

Summary by CodeRabbit

• New Features

  • Added support for Laravel 12, enhancing the package's compatibility with the latest framework version.

• Documentation

  • Updated the changelog with a new v1.0.7 entry, featuring a link to the full list of updates and revised documentation details.
  • Added a new instruction to the release process in the README for creating a changelog entry on the Ably platform.

• Chores

  • Bumped the overall package version to v1.0.7.

[coderabbitai]

Warning

Rate limit exceeded

@sacOO7 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 8 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 10a670a and 5731773.

📒 Files selected for processing (1)

• README.md (2 hunks)

Walkthrough

The changes introduce a version bump from 1.0.6 to 1.0.7 across the repository. The CHANGELOG.md now features a new entry for version 1.0.7 outlining updates—most notably, support for Laravel 12 (implemented in response to issue #58) along with links to the full changelog and merged pull requests (#59 and #57). In addition, the LIB_VERSION constant in the src/AblyBroadcaster.php file is updated to reflect this version change.

Changes

File(s)	Change Summary
CHANGELOG.md	Added a new version entry for v1.0.7 with details on Laravel 12 support, a link to the full changelog, and references to merged PRs (#59, #57) in response to issue #58.
src/AblyBroadcaster.php	Updated the constant LIB_VERSION from '1.0.6' to '1.0.7' to reflect the new version.
README.md	Added a new step in the release process to create an entry on the Ably Changelog after completing other steps.

Possibly related PRs

• [ECO-5208] Support laravel 12 #59: The changes in this PR focus on supporting Laravel 12 and include modifications to the src/AblyBroadcaster.php file regarding token expiry, directly connecting to the current PR.
• Release/1.0.6 #52: Updates the version constant from 1.0.5 to 1.0.6, directly preceding the current version bump to 1.0.7.

Suggested reviewers

• owenpearson
• ttypic

Poem

Hop, skip, and bump the version high,
I'm the rabbit with a twinkling eye.
Laravel 12 now joins the fun,
1.0.7 shines like the morning sun.
Cheers to updates that make our code run 🐇✨!

Happy coding in every leap and bound!

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 generate docstrings to generate docstrings for this 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.

[AndyTWF]

Aware it's somewhat obvious from the title, but can we make sure we have a PR description body please :)

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

CHANGELOG.md (2)

7-7: Markdown Style Consistency: Use Proper Heading

Instead of using bold emphasis for "Laravel 12 support," consider converting it into a Markdown heading (e.g., ### Laravel 12 support) for better clarity and consistency with common Markdown practices. This also addresses the markdownlint hint (MD036).

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

7-7: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

11-11: Section Header Formatting Consistency

The section title "Merged pull requests:" is presented in bold. For consistency with the rest of the changelog (which uses header styles for version entries), consider converting this to an appropriate Markdown heading (e.g., ### Merged pull requests:).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eeb1c3c and 6f9a1ab.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• src/AblyBroadcaster.php (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• src/AblyBroadcaster.php

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

CHANGELOG.md

7-7: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

🔇 Additional comments (4)

CHANGELOG.md (4)

3-3: Version Entry Consistency Check

The version entry for v1.0.7 is correctly formatted, including a link that points to the corresponding tag on GitHub. Ensure that this formatting remains consistent with previous version entries.

---

5-5: Full Changelog Link Verification

The changelog link clearly indicates the comparison between v1.0.6 and v1.0.7. Please verify that the URL directs to the expected diff on GitHub.

---

9-9: Feature Description Clarity

The bullet point succinctly describes the support added for Laravel 12 and accurately references issue #58. Good work ensuring that the description remains clear.

---

13-14: Merged Pull Requests Documentation

The entries for the merged pull requests are well documented, including clear references to pull request numbers and contributor names. Please double-check that all URLs and references are up to date.

[sacOO7]

Aware it's somewhat obvious from the title, but can we make sure we have a PR description body please :)

CoderabbitAI automatically generates : P