chore(repo): release v9.14.0 #2309
Conversation
WalkthroughThis change updates the version numbers of several related packages from 9.13.0 to 9.14.0 throughout the repository. The updates affect package manifests, changelogs, dependency constraints, and version constants, but do not introduce any code or logic modifications. Changes
Sequence Diagram(s)No sequence diagram generated as the changes are limited to version and dependency updates without control flow modifications. Possibly related PRs
Suggested reviewers
Poem
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: 0
🧹 Nitpick comments (3)
packages/stream_chat/CHANGELOG.md (1)
1-18: Consider adding a release date to the new 9.14.0 header.Most earlier sections include only the version, but many projects put the release date in brackets – e.g.
## 9.14.0 – 2025-07-01.
Adding the date helps readers quickly locate a particular drop.packages/stream_chat_flutter/CHANGELOG.md (1)
1-6: Nice concise entry; same date note as above.Optional: append the release date after the version header for consistency across packages.
packages/stream_chat_flutter_core/CHANGELOG.md (1)
1-7: Changelog entry LGTM – date would improve clarity.See earlier comments; otherwise no issues.
📜 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: test
- GitHub Check: build (ios)
- GitHub Check: build (android)
- GitHub Check: analyze
- GitHub Check: stream_chat_flutter_core
- GitHub Check: stream_chat_localizations
- GitHub Check: stream_chat_persistence
- GitHub Check: stream_chat_flutter
- GitHub Check: stream_chat
🔇 Additional comments (15)
packages/stream_chat/example/pubspec.yaml (1)
27-27: Version bump looks consistent – no concerns.The example app now pins to
stream_chat ^9.14.0, in-sync with the SDK release.
No additional action required.packages/stream_chat/pubspec.yaml (1)
4-4: Version bump confirmedVerified that
packages/stream_chat/lib/version.dartand all references use the updated version:
- packages/stream_chat/lib/version.dart:12
const PACKAGE_VERSION = '9.14.0';- packages/stream_chat/lib/src/client/client.dart:167
static const packageVersion = PACKAGE_VERSION;- packages/stream_chat/lib/src/core/http/system_environment_manager.dart:19
sdkVersion: PACKAGE_VERSION,Everything is consistent for this patch release.
packages/stream_chat_flutter_core/example/pubspec.yaml (1)
26-26: Dependency bump looks correct and consistent
The example now pullsstream_chat_flutter_core^9.14.0, matching the SDK release. No additional action needed.packages/stream_chat_persistence/CHANGELOG.md (1)
1-4: Changelog entry added correctly
Version header and bullet follow the existing format. ✔️packages/stream_chat_localizations/example/pubspec.yaml (1)
27-28: Example app versions aligned
Bothstream_chat_flutterandstream_chat_localizationsnow point to^9.14.0. Looks good.packages/stream_chat/lib/version.dart (1)
12-12: Central version constant updated
PACKAGE_VERSIONmoved to9.14.0, in sync with pubspecs. 👍packages/stream_chat_localizations/CHANGELOG.md (1)
1-4: Changelog increment is accurate
New section and dependency note added with correct link. Nothing else to flag.sample_app/pubspec.yaml (1)
37-39: Verify updated Stream package versions inpubspec.lockBefore merging, please ensure that all
pubspec.lockfiles reflect the bumped Stream package versions (9.14.0). You can run:# From the repo root grep -R -n 'stream_chat_flutter:' -A1 --include pubspec.lock . grep -R -n 'stream_chat_localizations:' -A1 --include pubspec.lock . grep -R -n 'stream_chat_persistence:' -A1 --include pubspec.lock .And confirm each shows:
version: "9.14.0"If any locks still list
9.13.x, runmelos bootstraporflutter pub getin that package and commit the updated lockfiles.packages/stream_chat_persistence/pubspec.yaml (1)
4-4: Package + dependency version aligned
version: 9.14.0and thestream_chatpeer dependency are bumped in lock-step — exactly what we want to avoid mixed minor versions at runtime.
Changelog already updated in the repo history, so nothing else required.Also applies to: 33-33
packages/stream_chat_flutter/pubspec.yaml (1)
4-4: Consistent minor update with core dependencyThe SDK and its
stream_chat_flutter_coredependency are both on^9.14.0; good catch keeping them in sync.
No additional concerns.Also applies to: 59-59
packages/stream_chat_flutter_core/pubspec.yaml (1)
4-4: Core package bump OKVersion and
stream_chatconstraint updated coherently.
All looks good.Also applies to: 34-34
packages/stream_chat_localizations/pubspec.yaml (1)
3-3: Localization package in sync
stream_chat_flutterpeer dependency follows the main SDK at^9.14.0; version header updated accordingly.
Nothing else to add.Also applies to: 29-29
packages/stream_chat_persistence/example/pubspec.yaml (1)
26-27: Double-check that 9.14.0 is published before mergingNothing else changed here, so the build will fail if any of the bumped packages haven’t yet landed on pub.dev.
Runmelos bootstrap(orflutter pub getin this example) on CI to confirm the tags exist.packages/stream_chat_flutter/example/pubspec.yaml (1)
28-30: Ensure all three bumped packages are simultaneously available on pub.devBecause these three packages depend on one another, publishing them out-of-order can briefly break
flutter pub getfor external consumers.
Verify the release pipeline publishesstream_chat_flutter,stream_chat_localizations, andstream_chat_persistence9.14.0 in a single run.melos.yaml (1)
83-87: Version list looks consistent — trigger a fullmelos bootstrapbefore taggingThe central constraints now point to 9.14.0 for all Stream packages.
Run the bootstrap step locally (or on CI) to regeneratepubspec.lockfiles and to update the generatedversion.dart. This prevents consumers from accidentally getting a mixed 9.13.x / 9.14.0 state.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2309 +/- ##
=======================================
Coverage 63.55% 63.56%
=======================================
Files 409 409
Lines 25571 25571
=======================================
+ Hits 16251 16253 +2
+ Misses 9320 9318 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
What's Changed
client.getUnreadCount()by @xsahil03x in feat(llc): add support forclient.getUnreadCount()#2300Full Changelog: v9.13.0...v9.14.0
Summary by CodeRabbit