Update changelog for main

[github-actions]

This PR updates the changelog with the latest changes.

Summary by Sourcery

文档：

• 在主要发行版的更新日志中记录针对首次路径匹配错误的修复。

Original summary in English

Summary by Sourcery

Documentation:

• Document the fix for the first path matching error in the main release changelog.

[sourcery-ai]

审阅者指南（在小型 PR 上折叠）

审阅者指南

更新主分支的变更日志，包含一个与首个路径匹配错误相关的已修复 bug，以保持发行说明的实时性。

文件级变更

Change	Details	Files
在主分支的变更日志中，在 Bug 修复（Bug Fix）部分记录一个新修复的 bug。	添加一个项目符号，描述对首个路径匹配错误的修复，包含 PR 编号和作者署名 将这个新的 bug 修复条目放在主版本现有的其他 bug 修复条目旁边	CHANGELOG.md

---

技巧与命令

与 Sourcery 交互

• 触发新的审阅： 在 pull request 中评论 @sourcery-ai review。
• 继续讨论： 直接回复 Sourcery 的审阅评论。
• 从审阅评论生成 GitHub issue： 通过回复某条审阅评论来让 Sourcery 从该评论创建一个 issue。你也可以在审阅评论下回复 @sourcery-ai issue 来从该评论创建 issue。
• 生成 pull request 标题： 在 pull request 标题中的任意位置写入 @sourcery-ai，即可随时生成标题。你也可以在 pull request 中评论 @sourcery-ai title 来（重新）生成标题。
• 生成 pull request 摘要： 在 pull request 正文的任意位置写入 @sourcery-ai summary，即可在你想要的确切位置随时生成 PR 摘要。你也可以在 pull request 中评论 @sourcery-ai summary 来在任意时间（重新）生成摘要。
• 生成审阅者指南： 在 pull request 中评论 @sourcery-ai guide，即可在任意时间（重新）生成审阅者指南。
• 解决所有 Sourcery 评论： 在 pull request 中评论 @sourcery-ai resolve，即可解决所有 Sourcery 评论。如果你已经处理完所有评论且不想再看到它们，这将非常有用。
• 撤销所有 Sourcery 审阅： 在 pull request 中评论 @sourcery-ai dismiss，即可撤销所有现有的 Sourcery 审阅。如果你想重新开始一次全新的审阅，这尤其有用——别忘了再评论 @sourcery-ai review 来触发新的审阅！

自定义你的体验

访问你的控制面板以：

• 启用或禁用审阅功能，例如 Sourcery 生成的 pull request 摘要、审阅者指南等。
• 更改审阅语言。
• 添加、移除或编辑自定义审阅指令。
• 调整其他审阅设置。

获取帮助

• 如有问题或反馈，请联系支持团队。
• 访问我们的文档获取详细指南和信息。
• 通过在 X/Twitter、LinkedIn 或 GitHub 关注我们，与 Sourcery 团队保持联系。

Original review guide in English

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Update the main branch changelog to include a newly fixed bug related to first path matching errors, keeping the release notes current.

File-Level Changes

Change	Details	Files
Document a newly fixed bug in the main branch changelog under the Bug Fix section.	Add a bullet describing the fix for the first path matching error, including PR number and author attribution Place the new bug fix entry alongside other existing bug fixes for the main release	CHANGELOG.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - 我发现了两个问题，并留下了一些总体反馈：

• 新的 changelog 条目使用了首字母大写的 Fix:，而周围的条目使用的是小写的 fix:；为了保持一致性，建议将大小写与现有风格对齐。
• 短语 the issue with the first path matching error 略显冗余；为了更清晰，建议简化为 Fix: first path matching error 或 Fix: error in first path matching 之类的表述。

给 AI Agent 的提示

Please address the comments from this code review:

## Overall Comments
- The new changelog entry uses `Fix:` with an uppercase F while the surrounding entries use `fix:`; consider aligning the capitalization with the existing style for consistency.
- The phrase `the issue with the first path matching error` is slightly redundant; consider simplifying to something like `Fix: first path matching error` or `Fix: error in first path matching` for clarity.

## Individual Comments

### Comment 1
<location path="CHANGELOG.md" line_range="12" />
<code_context>

 #### Bug Fix
+* Fix: the issue with the first path matching error [#11798](https://github.com/deepflowio/deepflow/pull/11798) by [yuanchaoa](https://github.com/yuanchaoa)
 * fix: agnet - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)
 * fix: agent - eBPF Fix Crashes Caused by Packet Count Statistics [#8816](https://github.com/deepflowio/deepflow/pull/8816) by [yinjiping](https://github.com/yinjiping)
 * fix: wan type cidr may not be tagged [#8814](https://github.com/deepflowio/deepflow/pull/8814) by [lzf575](https://github.com/lzf575)
</code_context>
<issue_to_address>
**issue (typo):** Typo: "agnet" should be "agent".

Please change "agnet" to "agent" in this entry.

```suggestion
* fix: agent - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)
```
</issue_to_address>

### Comment 2
<location path="CHANGELOG.md" line_range="14" />
<code_context>
+* Fix: the issue with the first path matching error [#11798](https://github.com/deepflowio/deepflow/pull/11798) by [yuanchaoa](https://github.com/yuanchaoa)
 * fix: agnet - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)
 * fix: agent - eBPF Fix Crashes Caused by Packet Count Statistics [#8816](https://github.com/deepflowio/deepflow/pull/8816) by [yinjiping](https://github.com/yinjiping)
 * fix: wan type cidr may not be tagged [#8814](https://github.com/deepflowio/deepflow/pull/8814) by [lzf575](https://github.com/lzf575)
</code_context>
<issue_to_address>
**suggestion (typo):** Consider capitalizing standard acronyms "WAN" and "CIDR".

Align with networking terminology by writing this as "WAN type CIDR", capitalizing both acronyms.
</issue_to_address>

---

Sourcery 对开源项目免费——如果你觉得我们的代码审查有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请在每条评论上点击 👍 或 👎，我会根据你的反馈改进后续的代码审查。}

Original comment in English

Hey - I've found 2 issues, and left some high level feedback:

• The new changelog entry uses Fix: with an uppercase F while the surrounding entries use fix:; consider aligning the capitalization with the existing style for consistency.
• The phrase the issue with the first path matching error is slightly redundant; consider simplifying to something like Fix: first path matching error or Fix: error in first path matching for clarity.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new changelog entry uses `Fix:` with an uppercase F while the surrounding entries use `fix:`; consider aligning the capitalization with the existing style for consistency.
- The phrase `the issue with the first path matching error` is slightly redundant; consider simplifying to something like `Fix: first path matching error` or `Fix: error in first path matching` for clarity.

## Individual Comments

### Comment 1
<location path="CHANGELOG.md" line_range="12" />
<code_context>

 #### Bug Fix
+* Fix: the issue with the first path matching error [#11798](https://github.com/deepflowio/deepflow/pull/11798) by [yuanchaoa](https://github.com/yuanchaoa)
 * fix: agnet - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)
 * fix: agent - eBPF Fix Crashes Caused by Packet Count Statistics [#8816](https://github.com/deepflowio/deepflow/pull/8816) by [yinjiping](https://github.com/yinjiping)
 * fix: wan type cidr may not be tagged [#8814](https://github.com/deepflowio/deepflow/pull/8814) by [lzf575](https://github.com/lzf575)
</code_context>
<issue_to_address>
**issue (typo):** Typo: "agnet" should be "agent".

Please change "agnet" to "agent" in this entry.

```suggestion
* fix: agent - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)
```
</issue_to_address>

### Comment 2
<location path="CHANGELOG.md" line_range="14" />
<code_context>
+* Fix: the issue with the first path matching error [#11798](https://github.com/deepflowio/deepflow/pull/11798) by [yuanchaoa](https://github.com/yuanchaoa)
 * fix: agnet - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)
 * fix: agent - eBPF Fix Crashes Caused by Packet Count Statistics [#8816](https://github.com/deepflowio/deepflow/pull/8816) by [yinjiping](https://github.com/yinjiping)
 * fix: wan type cidr may not be tagged [#8814](https://github.com/deepflowio/deepflow/pull/8814) by [lzf575](https://github.com/lzf575)
</code_context>
<issue_to_address>
**suggestion (typo):** Consider capitalizing standard acronyms "WAN" and "CIDR".

Align with networking terminology by writing this as "WAN type CIDR", capitalizing both acronyms.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (typo): 拼写错误："agnet" 应为 "agent"。

请在这一条目中将 "agnet" 修改为 "agent"。

Suggested change

	* fix: agnet - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)
	* fix: agent - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)

Original comment in English

issue (typo): Typo: "agnet" should be "agent".

Please change "agnet" to "agent" in this entry.

Suggested change

	* fix: agnet - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)
	* fix: agent - eBPF Fix the kernel kick on CPU0 was not triggered [#8817](https://github.com/deepflowio/deepflow/pull/8817) by [yinjiping](https://github.com/yinjiping)

[sourcery-ai]

suggestion (typo): 建议将常用缩写 "WAN" 和 "CIDR" 都写成大写。

为与网络术语保持一致，建议将其写作 "WAN type CIDR"，并将这两个缩写都大写。

Original comment in English

suggestion (typo): Consider capitalizing standard acronyms "WAN" and "CIDR".

Align with networking terminology by writing this as "WAN type CIDR", capitalizing both acronyms.