Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

"Unable to resolve action..." warning doesn't disappear after finishing edit

Open
#409 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, typescript, vscode
Domain
ci-cd, devtools

Research direction

No files or tests are named. Start by tracing the extension's action-reference validation and diagnostic refresh when a workflow action version is edited in place, then try reproducing the stale warning; done means the diagnostic reflects the final version without requiring a VS Code restart.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
Occasionally, when I edit a referenced action version, a warning about the non-existing version appears during editing and doesn't disappear after finishing the edit. For example, I changed the action from slidoapp/xcresulttool@v2.0.0 to slidoapp/xcresulttool@v3.1.0 by deleting "2.0" and replacing it with "3.1". However, the warning got stuck on "Unable to resolve action slidoapp/xcresulttool@v.0.0, repository or version not found." Even closing and reopening the workflow file didn't help, I had to restart VSCode to get rid of that warning message.

To Reproduce
Difficult to reproduce, it happens randomly while editing the referenced actions

Expected behavior
After finishing the edit, the plugin re-checks the existence of the final version of the action being edited (v3.1.0, not v.0.0).

Screenshots
image

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

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

More from github/vscode-github-actions

All issues in github/vscode-github-actions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.