chore(repo): release v9.15.0 #2331
Conversation
WalkthroughThis update increments the version numbers of the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (18)
✅ Files skipped from review due to trivial changes (10)
🚧 Files skipped from review as they are similar to previous changes (8)
⏰ 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). (8)
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (4)
packages/stream_chat_flutter_core/CHANGELOG.md (1)
1-1: Consider appending a release date to the new headerMost changelogs in the repo include the version and the release date (e.g.
## 9.15.0 – 2024-07-10).
Adding it keeps history uniform and helps external consumers.packages/stream_chat_flutter/CHANGELOG.md (1)
1-1: Add release date for completenessSame remark as in the core changelog: including a date after the version improves traceability.
packages/stream_chat_persistence/CHANGELOG.md (1)
1-1: Release header is missing a dateAppending the actual release date keeps this changelog in line with the others.
packages/stream_chat/CHANGELOG.md (1)
1-11: Add a release date to keep the changelog machine-friendlyEvery previous section starts with a version header but omits the release date. While that is acceptable, adding an ISO-8601 date after the version (e.g.
## 9.15.0 – 2025-07-xx) helps automated tooling (Melos,release-please, etc.) and human readers quickly identify when a version shipped.-## 9.15.0 +## 9.15.0 – 2025-07-??
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (18)
melos.yaml(1 hunks)packages/stream_chat/CHANGELOG.md(1 hunks)packages/stream_chat/example/pubspec.yaml(1 hunks)packages/stream_chat/lib/version.dart(1 hunks)packages/stream_chat/pubspec.yaml(1 hunks)packages/stream_chat_flutter/CHANGELOG.md(1 hunks)packages/stream_chat_flutter/example/pubspec.yaml(1 hunks)packages/stream_chat_flutter/pubspec.yaml(2 hunks)packages/stream_chat_flutter_core/CHANGELOG.md(1 hunks)packages/stream_chat_flutter_core/example/pubspec.yaml(1 hunks)packages/stream_chat_flutter_core/pubspec.yaml(2 hunks)packages/stream_chat_localizations/CHANGELOG.md(1 hunks)packages/stream_chat_localizations/example/pubspec.yaml(1 hunks)packages/stream_chat_localizations/pubspec.yaml(2 hunks)packages/stream_chat_persistence/CHANGELOG.md(1 hunks)packages/stream_chat_persistence/example/pubspec.yaml(1 hunks)packages/stream_chat_persistence/pubspec.yaml(2 hunks)sample_app/pubspec.yaml(1 hunks)
⏰ 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). (10)
- GitHub Check: analyze_legacy_versions
- GitHub Check: stream_chat_localizations
- GitHub Check: stream_chat_flutter
- GitHub Check: stream_chat_flutter_core
- GitHub Check: stream_chat_persistence
- GitHub Check: stream_chat
- GitHub Check: build (android)
- GitHub Check: build (ios)
- GitHub Check: test
- GitHub Check: analyze
🔇 Additional comments (15)
melos.yaml (1)
83-87: Dependency bump confirmed – no leftover version constraintsI ran the suggested grep across the repo and only found
9.14.0references in CHANGELOG.md files (historical entries). No manifests or pubspecs still constrain9.14.x. You’re clear to merge.packages/stream_chat/pubspec.yaml (1)
4-4: VERSION CONSTANT SYNCED – PLEASE VERIFY GIT TAGThe
PACKAGE_VERSIONconstant inpackages/stream_chat/lib/version.dartis correctly set to9.15.0. Before merging, please ensure that the release workflow also creates a Git tag reading9.15.0(orv9.15.0) so thatStreamChatClient.clientVersioncontinues to function as expected.• Verified in
packages/stream_chat/lib/version.dart(line 12):
const PACKAGE_VERSION = '9.15.0';
• Next step: confirm the corresponding Git tag exists in your release branch.packages/stream_chat/example/pubspec.yaml (1)
27-27: Dependency bump looks good – example now points to^9.15.0, staying in lock-step with the core package.packages/stream_chat_flutter_core/example/pubspec.yaml (1)
26-26: Version synced correctly – example depends onstream_chat_flutter_core ^9.15.0; no further action required.packages/stream_chat_localizations/example/pubspec.yaml (1)
27-29: All related example dependencies updated consistently – bothstream_chat_flutterandstream_chat_localizationsare bumped to^9.15.0.
Nothing else to flag.packages/stream_chat/lib/version.dart (1)
12-12: Version constant bumped – looks correct
The constant now reflects9.15.0, matching the release tag across the repo.packages/stream_chat_persistence/example/pubspec.yaml (1)
26-27: Example aligned with new major-minor version
Caret constraints updated to^9.15.0; nothing else required. Remember to runmelos bootstrapso the example’s lockfile stays in sync.sample_app/pubspec.yaml (1)
37-39: Sample app dependencies updated – all good
Versions are consistent with the core packages. Regeneratepubspec.lockafter bootstrapping to avoid mix-matched versions during CI.packages/stream_chat_flutter/pubspec.yaml (2)
4-4: Package version updated – verify CHANGELOG before publishing
Ensure theCHANGELOG.mdhas an entry for9.15.0so pub.dev displays correct release notes.
59-59: Dependency bump consistent with ecosystem
stream_chat_flutter_coremoved to^9.15.0; everything remains internally compatible.packages/stream_chat_persistence/pubspec.yaml (2)
4-4: Version bump OK
Library version now at9.15.0, matching the rest of the suite.
33-33: Dependency constraint updated correctly
stream_chatraised to^9.15.0; no other changes needed.packages/stream_chat_flutter/example/pubspec.yaml (1)
28-30: Version bumps look correct.
The example app now points to the freshly-released 9.15.0 artifacts – nothing else to flag here.packages/stream_chat_flutter_core/pubspec.yaml (1)
4-4: Package & peer-dependency version aligned.
stream_chat_flutter_coreis correctly bumped to 9.15.0 and itsstream_chatpeer moves in lock-step. Looks good.Also applies to: 34-34
packages/stream_chat_localizations/pubspec.yaml (1)
3-3: pubspec version bump is consistent.
Version and dependency constraints both reflect 9.15.0 – no issues spotted.Also applies to: 29-29
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2331 +/- ##
=======================================
Coverage 63.65% 63.65%
=======================================
Files 409 409
Lines 25617 25617
=======================================
Hits 16306 16306
Misses 9311 9311 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
xsahil03x
force-pushed
the
release/v9.15.0
branch
from
253d1cd to
317c0a0
Compare
What's Changed
avgResponseTimeto User model by @xsahil03x in feat(llc, persistence): addavgResponseTimeto User model #2322New Contributors
Full Changelog: v9.14.0...v9.15.0
Summary by CodeRabbit