api-docs: Update feature level 256 changelog and changes notes.

The original feature level updates were made in commit de90d0acdf.
This commit is contained in:
Lauryn Menard 2024-05-27 20:14:32 +02:00 committed by Tim Abbott
parent 3971c033c3
commit 842fdb55d3
2 changed files with 17 additions and 7 deletions

View File

@ -79,8 +79,10 @@ format used by the Zulip server that they are interacting with.
**Feature level 256**
* [`GET /events`](/api/get-events): Stream update events with a new
`first_message_id` may now be sent when messages are deleted.
* [`POST /streams/{stream_id}/delete_topic`](/api/delete-topic),
[`GET /events`](/api/get-events): When messages are deleted, a
[`stream` op: `update`](/api/get-events#stream-update) event with
an updated value for `first_message_id` may now be sent to clients.
**Feature level 255**

View File

@ -1401,7 +1401,14 @@ paths:
- type: object
description: |
Event sent to all users who can see that a channel exists
when a property of that channel changes.
when a property of that channel changes. See
[GET /streams](/api/get-streams#response) response
for details on the various properties of a channel.
**Changes**: Before Zulip 9.0 (feature level 256), this event
was never sent when the `first_message_id` property of a channel
was updated because the oldest message that had been sent to it
changed.
properties:
id:
$ref: "#/components/schemas/EventIdSchema"
@ -1426,8 +1433,8 @@ paths:
type: string
description: |
The property of the channel which has changed. See
[GET /stream](/api/get-streams) for details on the various
properties of a channel.
[GET /streams](/api/get-streams#response) response for details
on the various properties of a channel.
Clients should handle an "unknown" property received here without
crashing, since that can happen when connecting to a server running a
@ -18421,8 +18428,9 @@ paths:
response will return `"complete": true`.
**Changes**: Before Zulip 9.0 (feature level 256), the server never sent
events updating the `first_message_id` for a channel when the oldest
message that had been sent to it changed.
[`stream` op: `update`](/api/get-events#stream-update) events with an
updated `first_message_id` for a channel when the oldest message that
had been sent to it changed.
Before Zulip 8.0 (feature level 211), if the server's
processing was interrupted by a timeout, but some messages in the topic