fix:修复ci报错

[Petterpx]

Sourcery 总结

通过更新 Android Gradle 插件和 Gradle Wrapper 版本来解决 CI 错误

错误修复：

• 将 Android Gradle 插件从 8.10.1 升级到 8.12.1
• 将 Gradle Wrapper 分发版升级到 8.14.3

Original summary in English

Summary by Sourcery

Resolve CI errors by updating Android Gradle Plugin and Gradle Wrapper versions

Bug Fixes:

• Bump Android Gradle Plugin from 8.10.1 to 8.12.1
• Upgrade Gradle Wrapper distribution to 8.14.3

[Copilot]

Pull Request Overview

This PR addresses CI failures by updating Gradle and Android Gradle Plugin versions, and modifying the Maven publishing workflow configuration.

• Updated Gradle version from 8.11.1 to 8.14.3
• Updated Android Gradle Plugin version from 8.10.1 to 8.12.1
• Added isPublish=true parameter to the Maven publishing command

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
gradle/wrapper/gradle-wrapper.properties	Updates Gradle wrapper to version 8.14.3
gradle/libs.versions.toml	Updates Android Gradle Plugin to version 8.12.1
.github/workflows/publish_maven.yml	Adds isPublish parameter to publishing command

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sourcery-ai]

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

审阅者指南

此 PR 通过将 Android Gradle 插件和 Gradle 包装器升级到新版本，并在 Maven 发布工作流文件中添加一个缺失的换行符，来解决 CI 故障。

带有换行符修复的 Maven 发布工作流流程图

flowchart TD
    Start[Start Workflow]
    Gradle[Run Gradle publishAndReleaseToMavenCentral]
    End[End Workflow]
    Start --> Gradle --> End

Loading

文件级别更改

更改	详情	文件
更新 Android Gradle 插件版本	插件版本从 8.10.1 更新到 8.12.1	gradle/libs.versions.toml
更新 Gradle 包装器分发	distributionUrl 从 gradle-8.11.1-all.zip 更改为 gradle-8.14.3-all.zip	gradle/wrapper/gradle-wrapper.properties
在 CI 工作流文件末尾添加换行符	在 publish_maven.yml 中插入了缺失的文件末尾换行符	.github/workflows/publish_maven.yml

---

提示和命令

与 Sourcery 互动

• 触发新审阅： 在拉取请求（pull request）上评论 @sourcery-ai review。
• 继续讨论： 直接回复 Sourcery 的审阅评论。
• 从审阅评论生成 GitHub issue： 通过回复审阅评论，让 Sourcery 创建一个 issue。您也可以回复审阅评论并带上 @sourcery-ai issue 来创建 issue。
• 生成拉取请求标题： 在拉取请求标题的任意位置写入 @sourcery-ai 即可随时生成标题。您也可以在拉取请求上评论 @sourcery-ai title 来随时（重新）生成标题。
• 生成拉取请求摘要： 在拉取请求正文的任意位置写入 @sourcery-ai summary 即可随时在您想要的位置生成拉取请求摘要。您也可以在拉取请求上评论 @sourcery-ai summary 来随时（重新）生成摘要。
• 生成审阅者指南： 在拉取请求上评论 @sourcery-ai guide 即可随时（重新）生成审阅者指南。
• 解决所有 Sourcery 评论： 在拉取请求上评论 @sourcery-ai resolve 以解决所有 Sourcery 评论。如果您已经处理了所有评论，并且不想再看到它们，这会很有用。
• 驳回所有 Sourcery 审阅： 在拉取请求上评论 @sourcery-ai dismiss 以驳回所有现有的 Sourcery 审阅。如果您想重新开始一个新审阅，这会特别有用——别忘了评论 @sourcery-ai review 来触发新审阅！

自定义您的体验

访问您的仪表板以：

• 启用或禁用审阅功能，例如 Sourcery 生成的拉取请求摘要、审阅者指南等。
• 更改审阅语言。
• 添加、删除或编辑自定义审阅说明。
• 调整其他审阅设置。

获取帮助

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

Original review guide in English

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR resolves CI failures by upgrading the Android Gradle Plugin and Gradle wrapper to newer versions and adding a missing newline in the Maven publish workflow file.

Flow diagram for Maven publish workflow with newline fix

flowchart TD
    Start[Start Workflow]
    Gradle[Run Gradle publishAndReleaseToMavenCentral]
    End[End Workflow]
    Start --> Gradle --> End

Loading

File-Level Changes

Change	Details	Files
Bump Android Gradle Plugin version	Updated plugin version from 8.10.1 to 8.12.1	gradle/libs.versions.toml
Update Gradle wrapper distribution	Changed distributionUrl from gradle-8.11.1-all.zip to gradle-8.14.3-all.zip	gradle/wrapper/gradle-wrapper.properties
Add newline at end of CI workflow file	Inserted missing end-of-file newline in publish_maven.yml	.github/workflows/publish_maven.yml

---

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]

你好 - 我已经审查了你的更改，它们看起来很棒！

---

Sourcery 对开源项目免费 - 如果您喜欢我们的评论，请考虑分享它们 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮助我变得更有用！请在每条评论上点击 👍 或 👎，我将利用这些反馈来改进我的评论。}

Original comment in English

Hey there - I've reviewed your changes and they look great!

---

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.}