v9.0.0 #1476
Draft
v9.0.0 #1476
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix: `channel_role` has been removed from the type of the `members` parameter of the `Channel.inviteMembers` method fix: properties `created_by` and `created_by_id` have been added to `ChannelData` and `ChannelQueryOptions` types BREAKING CHANGE: dropped jsDelivr bundle (#1468) BREAKING CHANGE: dropped `StreamChatGenerics`, use `Custom<Entity>Data` to extend your types BREAKING CHANGE: type `InviteOptions` has been renamed to `UpdateChannelOptions` BREAKING CHANGE: type `UpdateChannelOptions` has been renamed to `UpdateChannelTypeRequest` BREAKING CHANGE: type `ThreadResponseCustomData` has been renamed to `CustomThreadData` BREAKING CHANGE: type `MarkAllReadOptions` has been deleted in favour of type `MarkChannelsReadOptions` BREAKING CHANGE: type `QueryFilter` no longer supports `$ne` and `$nin` operators BREAKING CHANGE: type `ChannelMembership` has been deleted in favour of type `ChannelMemberResponse` BREAKING CHANGE: function `formatMessage` (`utils.ts`) no longer returns `__html` property in the formatted message output
## [9.0.0-rc.1](v8.57.1...v9.0.0-rc.1) (2025-02-27) ### ⚠ BREAKING CHANGES * dropped jsDelivr bundle (#1468) * dropped `StreamChatGenerics`, use `Custom<Entity>Data` to extend your types * type `InviteOptions` has been renamed to `UpdateChannelOptions` * type `UpdateChannelOptions` has been renamed to `UpdateChannelTypeRequest` * type `ThreadResponseCustomData` has been renamed to `CustomThreadData` * type `MarkAllReadOptions` has been deleted in favour of type `MarkChannelsReadOptions` * type `QueryFilter` no longer supports `$ne` and `$nin` operators * type `ChannelMembership` has been deleted in favour of type `ChannelMemberResponse` * function `formatMessage` (`utils.ts`) no longer returns `__html` property in the formatted message output ### Bug Fixes * replace StreamChatGenerics with module augmentation ([#1458](#1458)) ([feb97da](feb97da))
## [9.0.0-rc.2](v9.0.0-rc.1...v9.0.0-rc.2) (2025-02-27) ### Bug Fixes * increase package.json[engines.node] version ([6764bad](6764bad))
|
Size Change: -235 kB (-44.77%) 🎉 Total Size: 290 kB
|
## [9.0.0-rc.3](v9.0.0-rc.2...v9.0.0-rc.3) (2025-02-27) ### Bug Fixes * export promoteChannel ([#1474](#1474)) ([f2ba914](f2ba914))
## Description of the changes, What, Why and How? - upgraded Prettier to latest available version, adjusted configuration - upgraded ESLint to latest available version, added new configuration - dropped unused packages: - ESLint plugins (`eslint-config-prettier`, `eslint-plugin-markdown`, `eslint-plugin-prettier`, `eslint-plugin-sonarjs`, `eslint-plugin-typescript-sort-keys`) - `standard-version` - deprecated (previously used for versioning and CHANGELOG.md generation) - replaced `@typescript-eslint/eslint-plugin` & `@typescript-eslint/parser` with `typescript-eslint` - commit linting now happens through separate CI job (`pr-check.yml`), using `@commitlint/cli` - used both for `commit-msg` Husky hook and PR title check (with the same rules specified in `.commitlintrc.json`) #### Notable Changes: - added `GITHUB_TOKEN` for `@semantic-release/github` - use different @stream-ci-bot instead of @semantic-release-bot (1c313e8) - as part of this PR I've decided to migrate Mocha-based tests to Vitest, see [here](e68eb41)
## [9.0.0-rc.4](v9.0.0-rc.3...v9.0.0-rc.4) (2025-03-05) ### Bug Fixes * add extra user agent fields resolvable by react native ([#1477](#1477)) ([4232150](4232150)) * add missing env variable in rollup config ([#1480](#1480)) ([a935e9e](a935e9e)) * properly encode user agent on WS connection ([#1482](#1482)) ([58b538b](58b538b)) * remove pinned_at from the updateMessage api ([#1484](#1484)) ([7b73cac](7b73cac))
|
🎉 This PR is included in version 9.0.0-rc.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## CLA - [] I have signed the [Stream CLA](https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform) (required). - [] Code changes are tested ## Description of the changes, What, Why and How? When removing generics from stream-chat-angular I had an issue where augmenting the same custom interface (for example `CustomChannelData`) from two places (SDK and sample app) some changes were ignored (detailed description: https://getstream.slack.com/archives/C06CF5TKRGA/p1741163343794659). Found this open GH issue for TypeScript: microsoft/TypeScript#46617 https://linear.app/stream/issue/ANG-31/drop-generics ## Changelog -
## [9.0.0-rc.5](v9.0.0-rc.4...v9.0.0-rc.5) (2025-03-05) ### Bug Fixes * multiple module augmentation fails in Angular ([#1488](#1488)) ([7f8a9a0](7f8a9a0))
|
🎉 This PR is included in version 9.0.0-rc.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## Description of the changes, What, Why and How?
## Description of the changes, What, Why and How? Property `image` is considered a regular property according to the OpenAPI specification.
## [9.0.0-rc.6](v9.0.0-rc.5...v9.0.0-rc.6) (2025-03-06) ### Bug Fixes * add image property to UserResponse type ([#1486](#1486)) ([2a57b7f](2a57b7f))
|
🎉 This PR is included in version 9.0.0-rc.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
6 tasks
BREAKING CHANGE: `ErrorFromResponse` class constructor now requires second parameter (`status`, `response` and optionally `code`)
## [9.0.0-rc.7](v9.0.0-rc.6...v9.0.0-rc.7) (2025-03-11) ### ⚠ BREAKING CHANGES * `ErrorFromResponse` class constructor now requires second parameter (`status`, `response` and optionally `code`) ### Bug Fixes * adjust ErrorFromResponse error class ([#1491](#1491)) ([ff32bd2](ff32bd2))
|
🎉 This PR is included in version 9.0.0-rc.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## Description of the changes, What, Why and How?
## Description of the changes, What, Why and How?
|
🎉 This PR is included in version 9.0.0-rc.8 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.