Skip to content

fix: improve security update label formatting and translations#314

Open
xujin177 wants to merge 1 commit into
linuxdeepin:masterfrom
xujin177:bugfix/367957
Open

fix: improve security update label formatting and translations#314
xujin177 wants to merge 1 commit into
linuxdeepin:masterfrom
xujin177:bugfix/367957

Conversation

@xujin177

@xujin177 xujin177 commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Add proper labels for vulnerability IDs, severity, and descriptions in the update history dialog. Standardize label text with a trailing space for consistency between the update list and history dialog views. Update all translation files accordingly.

Log: Improved security update detail labels for better readability

Influence:

  1. Verify that vulnerability ID, severity, and description labels appear correctly in both the update list and history dialog
  2. Test with different update types (security vs version updates) to ensure proper label behavior
  3. Check that labels are properly translated in supported languages
  4. Verify that the history dialog correctly shows labels only for type=4 (security vulnerability) items
  5. Test with various severity levels and vulnerability IDs to ensure consistent display

fix: 改进安全更新标签格式和翻译

在更新历史对话框中为漏洞ID、严重级别和描述添加适当的标签。统一标签文本,
在更新列表和历史对话框视图之间保持一致。更新所有翻译文件。

Log: 改进安全更新详情标签,提升可读性

Influence:

  1. 验证漏洞ID、严重级别和描述标签在更新列表和历史对话框中正确显示
  2. 测试不同更新类型(安全更新与版本更新),确保标签行为正确
  3. 检查标签在支持的语言中是否正确翻译
  4. 验证历史对话框仅对类型为4(安全漏洞)的项显示标签
  5. 测试不同严重级别和漏洞ID,确保显示一致

PMS: BUG-367965 BUG-367957

Add proper labels for vulnerability IDs, severity, and descriptions in
the update history dialog. Standardize label text with a trailing space
for consistency between the update list and history dialog views. Update
all translation files accordingly.

Log: Improved security update detail labels for better readability

Influence:
1. Verify that vulnerability ID, severity, and description labels appear
correctly in both the update list and history dialog
2. Test with different update types (security vs version updates) to
ensure proper label behavior
3. Check that labels are properly translated in supported languages
4. Verify that the history dialog correctly shows labels only for type=4
(security vulnerability) items
5. Test with various severity levels and vulnerability IDs to ensure
consistent display

fix: 改进安全更新标签格式和翻译

在更新历史对话框中为漏洞ID、严重级别和描述添加适当的标签。统一标签文本,
在更新列表和历史对话框视图之间保持一致。更新所有翻译文件。

Log: 改进安全更新详情标签,提升可读性

Influence:
1. 验证漏洞ID、严重级别和描述标签在更新列表和历史对话框中正确显示
2. 测试不同更新类型(安全更新与版本更新),确保标签行为正确
3. 检查标签在支持的语言中是否正确翻译
4. 验证历史对话框仅对类型为4(安全漏洞)的项显示标签
5. 测试不同严重级别和漏洞ID,确保显示一致

PMS: BUG-367965 BUG-367957

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @xujin177, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@deepin-ci-robot

Copy link
Copy Markdown

Hi @xujin177. Thanks for your PR.

I'm waiting for a linuxdeepin member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@deepin-ci-robot

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: xionglinlin, xujin177

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants