GitHub Actions Extension Shows Incorrect Job Dependency Error (v0.28.0)

まず、サンプルの GitHub Actions workflow で診断を再現します。特に architecture-dependency-check を含む needs 配列に注目し、表示されたエラーと比較してください。拡張機能のジョブ依存関係の検証を追跡し、エラーが実際に参照されているジョブの名前を示していることを確認してください。workflow は誤った警告なしに実行を続ける必要があります。

Bug Report

Environment

• VS Code Version: 1.105.1 (user setup)
• GitHub Actions Extension Version: 0.28.0 (updated 3 weeks ago)
• OS: Windows_NT x64 10.0.26200
• Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084

Description

The GitHub Actions extension incorrectly validates job dependencies, showing an error for a non-existent job name instead of the actual job name defined in the workflow file.

Steps to Reproduce

1. Create a GitHub Actions workflow file with a job named architecture-dependency-check
2. Create another job that references this job in the needs: array
3. The extension shows a validation error referencing a completely different job name

Expected Behavior

The extension should validate job dependencies against the actual job names present in the current workflow file.

Actual Behavior

• Error message displayed: Job 'check-no-deployment' depends on unknown job 'foundation-architecture-scan'
• Actual file content: needs: [build-test, architecture-dependency-check]
• GitHub Actions execution result: Workflow runs successfully on GitHub

Sample Workflow Code

jobs:
  build-test:
    name: Build and Test
    runs-on: ubuntu-latest
    # ... job steps

  architecture-dependency-check:
    name: Architecture Dependency Check
    runs-on: ubuntu-latest
    # ... job steps

  check-no-deployment:
    name: Development Branch Status
    runs-on: ubuntu-latest
    needs: [build-test, architecture-dependency-check]  # This line shows the error
    # ... job steps

Workaround
Disabling and re-enabling the GitHub Actions extension temporarily resolves the issue.

Additional Context

• This issue appears to be related to the extension update from 3 weeks ago (version 0.28.0)
• The workflow file has been working correctly for weeks
• Multiple VS Code restarts do not resolve the issue
• The actual GitHub Actions execution works perfectly
  Impact
  While this doesn't affect functionality, it creates confusion and false error reporting in the development environment.