chore(deps): bump actions/checkout from 6.0.3 to 7.0.0

[dependabot]

Bumps actions/checkout from 6.0.3 to 7.0.0.

Release notes

Sourced from actions/checkout's releases.

v7.0.0

What's Changed

• block checking out fork pr for pull_request_target and workflow_run by @​aiqiaoy in actions/checkout#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 actions/checkout#2458
• Bump flatted from 3.3.1 to 3.4.2 by @​dependabot[bot] in actions/checkout#2460
• Bump js-yaml from 4.1.0 to 4.2.0 by @​dependabot[bot] in actions/checkout#2461
• Bump @​actions/core and @​actions/tool-cache and Remove uuid by @​dependabot[bot] in actions/checkout#2459
• upgrade module to esm and update dependencies by @​aiqiaoy in actions/checkout#2463
• Bump the minor-npm-dependencies group across 1 directory with 3 updates by @​dependabot[bot] in actions/checkout#2462
• getting ready for checkout v7 release by @​aiqiaoy in actions/checkout#2464
• update error wording by @​aiqiaoy in actions/checkout#2467

New Contributors

• @​aiqiaoy made their first contribution in actions/checkout#2454

Full Changelog: actions/checkout@v6.0.3...v7.0.0

Commits

• 9c091bb update error wording (#2467)
• 1044a6d getting ready for checkout v7 release (#2464)
• f028218 Bump the minor-npm-dependencies group across 1 directory with 3 updates (#2462)
• d914b26 upgrade module to esm and update dependencies (#2463)
• 537c7ef Bump @​actions/core and @​actions/tool-cache and Remove uuid (#2459)
• 130a169 Bump js-yaml from 4.1.0 to 4.2.0 (#2461)
• 7d09575 Bump flatted from 3.3.1 to 3.4.2 (#2460)
• 0f9f3aa Bump actions/publish-immutable-action (#2458)
• f9e715a block checking out fork pr for pull_request_target and workflow_run (#2454)
• See full diff in compare view

[dependabot]

Labels

The following labels could not be found: github-actions. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mikespreitzer for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[github-actions]

👋 Hey @dependabot[bot] — thanks for opening this PR!

🤖 This project is developed exclusively using AI coding assistants.

Please do not attempt to code anything for this project manually.
All contributions should be authored using an AI coding tool such as:

• Claude Code (Opus 4.5 / 4.6) — recommended
• GitHub Copilot
• Cursor
• Other AI coding assistants

This ensures consistency in code style, architecture patterns, test coverage,
and commit quality across the entire codebase.

---

This is an automated message.

[github-actions]

✅ Test Coverage Check

All new source files in this PR have corresponding test files.

Checked web/src/hooks/ and web/src/components/ against origin/main.

[netlify]

✅ Deploy Preview for kubestellarconsole ready!

Name	Link
🔨 Latest commit	3cfe11c
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellarconsole/deploys/6a42857954a5000008bbb72e
😎 Deploy Preview	https://deploy-preview-19899.console-deploy-preview.kubestellar.io
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[clubanderson]

⚠️ Quality Review — Major Version Bump Risk

Breaking Change: Fork PR Checkout Blocked

actions/checkout v7.0.0 introduces a breaking security change: it blocks checking out fork PRs when triggered by pull_request_target or workflow_run events.

Impact Assessment

This repository has 8 workflows using pull_request_target:

Workflow	Risk
hold-issue-guard.yml	Low — already guards with head.repo.full_name == github.repository
hive-interactive.yml	Low — same guard present
greetings.yml	Low — metadata-only, unlikely to checkout fork code
pr-claude-notice.yml	Low — comment-only workflow
new-contributor-pr-gate.yml	Medium — needs verification it doesn't checkout fork code
tier-classifier.yml	Medium — runs on synchronize, may checkout code
copilot-automation.yml	Medium — runs on synchronize + ready_for_review
ai-fix.yml	Medium — triggers on PR open

CI Status

Multiple E2E checks failing (all 4 chromium shards + accessibility tests). These failures should be investigated to determine whether they are caused by the checkout v7 change or are pre-existing.

Recommendation

Before merging:

1. Verify that none of the pull_request_target workflows checkout fork PR code directly (those with head.repo.full_name == github.repository guards are already safe)
2. Confirm E2E failures are pre-existing (compare with main branch CI status)
3. Consider testing on a feature branch first given this is a major version bump

---

Filed by quality agent (ACMM L4/L6 — full mode)

[clubanderson]

Quality Review — actions/checkout v6.0.3 → v7.0.0

Risk Assessment

• Impact: High — this is a major version bump affecting 80+ workflow files
• CI Status: ✅ build-deploy.yml passes on this branch

Observations

1. SHA-pinned (9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0) — ✅ supply chain safe
2. No known vulnerabilities in v7.0.0
3. Major version bumps may have breaking changes in input/output semantics (e.g., fetch-depth, submodules, token scoping)

Recommendation

Verify that workflows using fetch-depth: 0 (like coverage-gate.yml, helm-release.yml) still behave correctly with v7's history fetching. The build-deploy CI passing is a good signal.

---

Reviewed by quality agent (ACMM L4/L6 — full mode)

[clubanderson]

⚙️ Scanner analysis: The test failures on this PR (chromium shards, Merge Test Reports, Update Mechanism Tests) are caused by the same main-branch regression tracked in #19981 (174 test failures from the useDemoMode mock change in commit 3c38db5). This PR only bumps actions/checkout versions in workflow YAML files and doesn't affect app code.

A fix for #19981 has been dispatched. Once that PR merges and main is green, this PR should pass CI on re-run.

[clubanderson]

🐝 Scanner note: This PR cannot be merged via automation — it touches workflow files and requires workflow scope which our OAuth token doesn't have. CI is all green. Needs manual merge by a maintainer.

Command: gh pr merge 19899 --repo kubestellar/console --admin --squash

[clubanderson]

🤖 Scanner analysis: E2E test shards fail at "Download build artifacts" step (7 consecutive run attempts). The Build Frontend job passes, but downstream Playwright test jobs cannot download the produced artifacts.

This actions/checkout v6→v7 major bump may require corresponding updates to actions/upload-artifact / actions/download-artifact versions in the Playwright E2E workflow for artifact compatibility.

Blocked from auto-fix: this PR modifies workflow files which require workflow token scope not available to the scanner.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.