chore(deps): update actions/checkout action to v7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	v6.0.3 → v7.0.0

---

Release Notes

actions/checkout (actions/checkout)

v7.0.0

Compare Source

• Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
• Bump actions/publish-immutable-action from 0.0.3 to 0.0.4 in the minor-actions-dependencies group across 1 directory by @​dependabot[bot] in #​2458
• Bump flatted from 3.3.1 to 3.4.2 by @​dependabot[bot] in #​2460
• Bump js-yaml from 4.1.0 to 4.2.0 by @​dependabot[bot] in #​2461
• Bump @​actions/core and @​actions/tool-cache and Remove uuid by @​dependabot[bot] in #​2459
• upgrade module to esm and update dependencies by @​aiqiaoy in #​2463
• Bump the minor-npm-dependencies group across 1 directory with 3 updates by @​dependabot[bot] in #​2462

v7

Compare Source

• Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
• Bump actions/publish-immutable-action from 0.0.3 to 0.0.4 in the minor-actions-dependencies group across 1 directory by @​dependabot[bot] in #​2458
• Bump flatted from 3.3.1 to 3.4.2 by @​dependabot[bot] in #​2460
• Bump js-yaml from 4.1.0 to 4.2.0 by @​dependabot[bot] in #​2461
• Bump @​actions/core and @​actions/tool-cache and Remove uuid by @​dependabot[bot] in #​2459
• upgrade module to esm and update dependencies by @​aiqiaoy in #​2463
• Bump the minor-npm-dependencies group across 1 directory with 3 updates by @​dependabot[bot] in #​2462

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[DeepDiver1975]

🤖 Automated review by Claude Code review agent.

Overview

This is an automated Renovate dependency bump that updates the actions/checkout GitHub Action from v6.0.3 to v7.0.0 across all four workflow files that use it. Each reference is SHA-pinned with a # v7.0.0 comment, which is the recommended supply-chain-safe pinning practice. This is a low-risk change.

Code quality / style

• The change preserves the existing SHA-pinning convention (actions/checkout@<sha> # v7.0.0).
• The new commit SHA (9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0) and version comment are consistent across all four files.

Specific suggestions

• Consistency check: passed. All four workflow files that use actions/checkout are bumped to the same v7.0.0 SHA in this PR:

  • .github/workflows/docker-build-native.yml
  • .github/workflows/docker-build.yml
  • .github/workflows/docker-hub-desc.yml
  • .github/workflows/lint-editorconfig.yml

  No stale v6 reference is left behind, so the major version is pinned uniformly.

• Scope check: passed. Only workflow YAML files under .github/workflows/ are modified (4 files, +4/-4). No Dockerfiles, scripts, or runtime code touched.

Potential issues / risks

• Runner Node version (v7 runs on Node 24): actions/checkout v7 bumped its runtime from Node 20 to Node 24. On GitHub-hosted ubuntu-latest runners this is fine — they ship a runner that supports the Node 24 action runtime. The matrix runner in docker-build-native.yml (runs-on: ${{ matrix.runner }}) should be verified to be a GitHub-hosted or up-to-date self-hosted runner; an older self-hosted runner agent could fail to execute a Node 24 action. If this repo only uses GitHub-hosted runners, there is no concern.
• Behavioral change in v7: v7 blocks checking out fork PR code under pull_request_target and workflow_run events. None of the touched workflows here use those triggers for the checkout step in a way that targets fork refs, so no functional regression is expected. Worth keeping in mind if such triggers are added later.
• Recommend a green CI run before merge to confirm the runner picks up the Node 24 action without issue.

Overall: safe to merge once CI is green.