chore: Bump version to 6.0.50

[wangrong1069]

As title.

Log: Bump version to 6.0.50

Summary by Sourcery

Chores:

• Bump deepin-album package version from 6.0.49.x/6.0.46.1 to 6.0.50.1 in linglong.yaml for all architectures.

[github-actions]

TAG Bot

TAG: 6.0.50
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR performs a straightforward version bump of the deepin-album package metadata to 6.0.50.1 across multiple architecture-specific linglong manifests, aligning previously divergent versions.

File-Level Changes

Change	Details	Files
Update package version to 6.0.50.1 across all linglong manifests.	Bump arm64 linglong package version from 6.0.49.1 to 6.0.50.1. Bump generic linglong package version from 6.0.49.1 to 6.0.50.1. Bump loong64 linglong package version from 6.0.49.1 to 6.0.50.1. Bump mips64 linglong package version from 6.0.46.1 to 6.0.50.1. Bump sw64 linglong package version from 6.0.49.1 to 6.0.50.1.	arm64/linglong.yaml linglong.yaml loong64/linglong.yaml mips64/linglong.yaml sw64/linglong.yaml

---

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

[deepin-ci-robot]

deepin pr auto review

这份 Git diff 主要展示了 deepin-album 项目从版本 6.0.49/6.0.46 升级到 6.0.50 的变更记录。虽然变更主要是版本号的更新，但涉及到多架构构建和版本发布，需要仔细审查。

以下是针对语法逻辑、代码质量、代码性能和代码安全的审查意见及改进建议：

1. 语法逻辑

• 版本号一致性：
  • 观察：所有的 linglong.yaml 文件（arm64, loong64, mips64, sw64, 以及根目录）中的版本号都已统一更新为 6.0.50.1。
  • 评价：逻辑正确，确保了多架构构建时版本的一致性。
• 变更日志格式：
  • 观察：debian/changelog 遵循了标准的 Debian 格式，包含了版本号、发行版、紧急度和维护者信息。
  • 评价：语法符合规范。

2. 代码质量

• 变更描述的准确性：
  • 问题：debian/changelog 中描述为 "chore: Update compiler flags for security enhancements"（更新编译器标志以增强安全性）。
  • 风险：在提供的 diff 中，我们只看到了版本号的变更，完全没有看到任何关于编译器标志（如 CFLAGS, CXXFLAGS）或构建脚本（如 CMakeLists.txt, Makefile, .pro 文件）的修改。
  • 建议：如果本次提交确实是为了更新编译标志，那么相关的代码变更文件缺失了。如果本次提交仅仅是版本号升级，那么 changelog 中的描述是错误的，具有误导性。建议修改 changelog 描述以匹配实际代码变更（例如改为 "New upstream release" 或 "Bump version to 6.0.50"）。

3. 代码性能

• 影响：由于主要是配置文件和元数据的更新，不涉及源代码逻辑，因此对运行时性能没有直接影响。
• 注意：如果 changelog 中提到的 "Update compiler flags" 确实存在但在 diff 中未显示，那么新的编译器标志（例如开启 -O2 或 -O3 优化，或 -flto 链接时优化）可能会影响编译后的二进制性能。但由于 diff 中未体现，无法评估。

4. 代码安全

• 潜在的安全隐患：
  • 问题：同样基于 changelog 描述与实际 diff 不符的问题。如果开发者声称进行了"安全增强"（例如开启 FORTIFY_SOURCE, Stack Canaries, PIE/PIC 等），但 diff 中未体现，这会导致以下风险：
    1. 审计盲区：安全审计人员无法验证是否真的应用了安全补丁或标志。
    2. 发布风险：用户可能误以为安装了包含安全修复的版本，但实际上可能只是版本号变了。
  • 建议：请务必确认 changelog 的内容与实际提交的代码变更相符。如果确实有针对安全的构建脚本修改，请确保它们被包含在提交中。

5. 版本号规范

• 观察：linglong.yaml 中使用的是 6.0.50.1（四位版本号），而 debian/changelog 中使用的是 6.0.50（三位版本号）。
• 建议：请确认项目的版本策略。
  • 通常 linglong.yaml 的 version 字段用于构建打包，而 changelog 用于上游发行版记录。
  • 如果 6.0.50 是上游版本，那么 linglong.yaml 中的 6.0.50.1 可能代表该上游版本的第一次打包（修订版）。这种差异在某些打包系统中是允许的，但需要确保构建系统能正确处理这种映射关系，以免造成版本回退或混淆。

总结与改进建议

1. 修正 Changelog：最紧迫的问题是修正 debian/changelog 中的描述。如果 diff 中没有代码逻辑变更，请将描述改为 "Bump version to 6.0.50" 或类似描述，不要声称修改了编译标志。
2. 补全变更：如果确实修改了编译器标志以增强安全性，请将修改构建脚本（如 .pro, CMakeLists.txt 或 linglong.yaml 中的 build 字段）的 diff 一并提交。
3. 检查 mips64 版本：diff 显示 mips64/linglong.yaml 是从 6.0.46.1 直接跳跃到 6.0.50.1，跳过了 6.0.49。请确认这是否符合预期（例如 mips64 架构之前是否滞后发布，现在正在追赶主线版本）。如果只是补齐版本号，这是合理的。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lzwind, wangrong1069

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

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

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

[deepin-bot]

TAG Bot

✅ Tag created successfully

📋 Tag Details

• Tag Name: 6.0.50
• Tag SHA: ac8012f674a4d21d3c0f2622f43d7e0891a0566c
• Commit SHA: 1e874c6845fd84ac315399565c2e0f36e8b8557c
• Tag Message:

  Release deepin-album 6.0.50
  
  

• Tagger:
  • Name: wangrong1069
• Distribution: unstable