> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/documentation/zh/chuang-jian-nei-rong/blocks/updates.md).

# 更新

向页面添加一个或多个更新——非常适合为你的站点添加更新日志

更新块可让你在任意页面添加更新日志。每条更新都包含日期和可选标签，且支持在其中放置任意块内容，包括文本、图片、代码块、列表等。

### 添加更新

在任意页面插入更新块。插入后，将鼠标悬停在现有更新的上方或下方，即可按顺序添加另一条更新。

如需更改日期格式，请点击块中的日期。你可以显示完整日期、简写日期或纯数字日期（例如 12/25/2025）。

### 标签

每条更新都可以有自己的标签。使用日期下方的标签选择器即可添加、移除或重新排序标签。

### RSS 源

任何包含更新块的页面都会自动生成 RSS 源，无需额外设置。

读者可以点击页面顶部的按钮打开订阅源，复制其 URL，并将其添加到自己常用的阅读器中。你发布的新更新会自动推送到该阅读器。

如果页面没有更新块，就不会有 RSS 源。只需在页面中添加一个更新块，即可生成 RSS 源。

#### 套餐可用性

付费套餐可使用更新块。如果看不到添加更新块的选项，请确认你的套餐是否包含此功能。

#### 如果订阅源没有显示

如果已发布页面上没有显示 RSS 按钮，请确认页面至少包含一个更新块。订阅源是否生成取决于页面中是否存在该块——如果缺少更新块，就不会生成订阅源。如果页面中已有更新块，但订阅源仍未显示，请联系 [GitBook 支持团队](https://www.gitbook.com/contact).

### 示例

{% updates format="full" %}
{% update date="2025-12-25" tags="beta" %}

## 全新更新

使用此块向用户介绍一项新更新。你可以在其中添加所需的其他块，包括图片、代码、列表等。
{% endupdate %}
{% endupdates %}

{% code overflow="wrap" %}

```markdown
{% updates format="full" %}
{% update date="2025-12-25" tags="beta" %}
## 一项全新更新

此块非常适合向用户详细介绍产品的一项全新更新。你可以轻松地在更新块中添加其他块，包括图片、代码、列表等。
{% endupdate %}
{% endupdates %}
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.com/docs/documentation/zh/chuang-jian-nei-rong/blocks/updates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
