"Unable to resolve action" for any action

Open

#433 opened on Dec 15, 2024 5 comments 35 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 52/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: github-actions, typescript, vscode
Domain: tooling

Research direction

Reproduce the diagnostics in .github/workflows/dotnet.yml using actions/checkout@v4 and actions/setup-dotnet@v4, then trace the extension's action-resolution entry point. Confirm the fix by opening the Problems tab and verifying that valid actions no longer produce false repository or version errors.

Written by the indexing model from the issue text.

Description

bug

Every action in an .yml file gives an error Unable to resolve action "actions/checkout@v4", repository or version not found - even fundamental stuff like - uses: actions/checkout@v4

To Reproduce

Make a file like this one (autogenerated by github.com):

name: .NET
on:
  push:
    branches: [ "main" ]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v4
    - name: Setup .NET
      uses: actions/setup-dotnet@v4
      with:
        dotnet-version: 9.0.x
    - name: Restore dependencies
      run: dotnet restore
    - name: Build
      run: dotnet build --no-restore

Open the Problems tab in VSCode.
Lines 9 and 11 now give an error:

[{
	"resource": "/[repo_path]/.github/workflows/dotnet.yml",
	"owner": "_generated_diagnostic_collection_name_#7",
	"severity": 8,
	"message": "Unable to resolve action `actions/checkout@v4`, repository or version not found",
	"startLineNumber": 9,
	"startColumn": 13,
	"endLineNumber": 9,
	"endColumn": 32
}]

Expected behavior
Expected no false errors.

Screenshots
Screenshot 2024-12-15 at 17 51 22

Extension Version
v0.27.0

Additional context
Add any other context about the problem here.

Dominant language: TypeScript
Stars: 661
Forks: 214
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Tapping "Use video" more than once submits the verification twice Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

bcgov/bc-wallet-mobile#4761 · 1 comment · Opened Sep 24, 2026
fix(pg-meta): schemas.update and schemas.remove DO blocks fail when a name contains "$$" Open

external-issue to-triage

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

supabase/supabase#50882 · Opened Sep 24, 2026
Azure Sandboxes: Small and ExtraSmall tiers always fail to deploy (disk request exceeds tier maximum) Open

area-deployment area-integrations triage:bot-seen

Difficulty 2/5 Half a day Newbie friendliness 86/100

microsoft/aspire#20459 · 1 comment · Opened Sep 24, 2026
Mobile builds drop the telemetry and crash-reporting keys, so opting in sends nothing Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

0xMiden/wallet#1118 · Opened Sep 24, 2026
[P3] Handle clipboard failures and announce copy status accessibly Open

refactor

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

nteract/semiotic#1534 · Opened Sep 24, 2026

More TypeScript issues