chore(repo): release v9.13.0 #2291
Conversation
WalkthroughThis update synchronizes the version numbers of all Changes
Sequence Diagram(s)No sequence diagram generated as the changes are limited to version and changelog updates. 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 (5)
packages/stream_chat_flutter/CHANGELOG.md (1)
1-8: Consider stamping the release with an explicit dateReaders often scan the changelog for both version and release date.
Appending a date after the version header maintains parity with earlier entries (e.g.## 9.10.0 – 2024-05-07) and eases auditing.-## 9.13.0 +## 9.13.0 – 2025-06-??packages/stream_chat_flutter_core/CHANGELOG.md (1)
1-7: Nice concise entry – add release date for consistencySame nitpick as the Flutter package: include the release date next to the version header for easier chronological scanning.
packages/stream_chat_persistence/CHANGELOG.md (1)
1-4: Changelog entry added – consider noting user-facing fixesEntry correctly references the version bump, but including a short “Bug fixes & improvements” line (matching other packages) helps external readers.
packages/stream_chat_localizations/CHANGELOG.md (1)
1-4: Changelog aligned – minor formatting suggestionFor consistency with earlier sections, append an empty line after the bullet list:
- - Updated `stream_chat_flutter` dependency to ... - + + - Updated `stream_chat_flutter` dependency to ... +packages/stream_chat/CHANGELOG.md (1)
1-4: Add release date & concrete notes for 9.13.0The new entry only states “Bug fixes and improvements”. Earlier releases list a date and at least one tangible bullet. For transparency and troubleshooting, please include:
- Release date (
## 9.13.0 – YYYY-MM-DD).- One-line summaries or links to the merged PRs/issues fixed.
This keeps the changelog consistent and useful.
📜 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 (10)
- GitHub Check: stream_chat_flutter
- GitHub Check: build (ios)
- GitHub Check: stream_chat_localizations
- GitHub Check: build (android)
- GitHub Check: test
- GitHub Check: analyze
- GitHub Check: stream_chat_flutter_core
- GitHub Check: stream_chat
- GitHub Check: analyze_legacy_versions
- GitHub Check: stream_chat_persistence
🔇 Additional comments (13)
packages/stream_chat_flutter_core/example/pubspec.yaml (1)
26-27: Version bump looks correctThe example now pulls
stream_chat_flutter_core: ^9.13.0, keeping it aligned with the library release. No further action needed.packages/stream_chat/pubspec.yaml (1)
4-4: VERSION CONSISTENCY VERIFIEDThe
PACKAGE_VERSIONconstant inpackages/stream_chat/lib/version.dartis set to9.13.0, matching the value inpackages/stream_chat/pubspec.yaml. No further changes required.packages/stream_chat/example/pubspec.yaml (1)
27-27: Example app dependency updated – LGTMThe example tracks
stream_chat: ^9.13.0, matching the core package. 👍packages/stream_chat_localizations/example/pubspec.yaml (1)
27-28: Version bump looks correct – please re-bootstrap before publishingBoth dependency constraints have been updated to
^9.13.0, which is consistent with the global release version.
After merging, remember to runmelos bootstrap && flutter pub getin the example folder to refresh the lock-file and verify that no transitive conflicts appear.packages/stream_chat/lib/version.dart (1)
12-12: Synced constant – double-check generator script is committed
PACKAGE_VERSIONnow matches the published tag.
To avoid drift, ensuretools/generate_version.dart(or CI step) was executed and that no other generated files need committing.sample_app/pubspec.yaml (1)
37-39: Sample app dependencies updated – run integration smoke-testsThe sample now pulls
^9.13.0for Flutter UI, localizations, and persistence.
Please build & launch the sample on a device to spot any breaking API changes that may have slipped through.packages/stream_chat_persistence/pubspec.yaml (1)
4-4: Version bump is consistent with the mono-repo release plan
Nothing else changes in this pubspec and the constraint^9.13.0keeps the caret semantics (<10.0.0). Looks good.Also applies to: 33-33
packages/stream_chat_flutter_core/pubspec.yaml (1)
4-4: Dependency & package version aligned correctly
The core package now self-reports9.13.0and depends onstream_chat ^9.13.0, matching other libs. No issues spotted.Also applies to: 34-34
packages/stream_chat_flutter/example/pubspec.yaml (1)
28-30: Examples updated to the new tag
The example app references all 9.13.0 artefacts, keeping it buildable against the release. 👍packages/stream_chat_persistence/example/pubspec.yaml (1)
26-27: Example dependency bump looks fine
Caret constraints updated; the change is trivial and safe.melos.yaml (1)
83-87: Melos workspace dependencies in sync
All workspace-wide overrides now target 9.13.0, somelos bootstrapwill pull the correct versions. 👍packages/stream_chat_flutter/pubspec.yaml (1)
4-4: Version bump confirmed – no stale 9.12.x references
I ranrg --glob '*pubspec.yaml' '9\.12\.[0-9]+' -nacross the repo and found no matches. All pubspecs are on 9.13.0. Ready to publish.packages/stream_chat_localizations/pubspec.yaml (1)
3-3: Version sync looks goodBoth the package’s own version and its dependency on
stream_chat_flutterare bumped to 9.13.0. No further action needed.Also applies to: 29-29
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2291 +/- ##
=======================================
Coverage 63.43% 63.43%
=======================================
Files 408 408
Lines 25555 25555
=======================================
Hits 16211 16211
Misses 9344 9344 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
What's Changed
Full Changelog: v9.12.0...v9.13.0
Summary by CodeRabbit