[BUG]: Error: Unable to resolve action octokit/[email protected], action not found

[nive-copia]

What happened?

This action stopped work starting from ~ 9:00 am pacific on 07-Feb-2025. There was no known changes to the environment on which it was running

Versions

octokit/[email protected]

Relevant log output

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[github-actions[bot]]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[borislavml]

We started having the same problem today. The weird part is that this happens for only one of our repos. We are using the action in several workflows in different repos and it's only in one place that if fails. We also haven't had ANY changes to the workflow or the way the action is used. It's literally a workflow that hasn't been touched for ages and just started failing with this error. We're using ubuntu-latest

Current runner version: '2.322.0'
Operating System
  Ubuntu
  24.04.1
  LTS
Runner Image
  Image: ubuntu-24.04
  Version: 20250202.1.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu24/20250202.1/images/ubuntu/Ubuntu2404-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20250202.1
Runner Image Provisioner
  2.0.422.1
GITHUB_TOKEN Permissions
  Checks: write
  Contents: write
  Metadata: read
  PullRequests: write
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Error: Unable to resolve action octokit/[email protected], action not found

[nive-copia]

We started having the same problem today. The weird part is that this happens for only one of our repos. We are using the action in several workflows in different repos and it's only in one place that if fails. We also haven't had ANY changes to the workflow or the way the action is used. It's literally a workflow that hasn't been touched for ages and just started failing with this error. We're using ubuntu-latest

Current runner version: '2.322.0'
Operating System
  Ubuntu
  24.04.1
  LTS
Runner Image
  Image: ubuntu-24.04
  Version: 20250202.1.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu24/20250202.1/images/ubuntu/Ubuntu2404-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20250202.1
Runner Image Provisioner
  2.0.422.1
GITHUB_TOKEN Permissions
  Checks: write
  Contents: write
  Metadata: read
  PullRequests: write
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Error: Unable to resolve action octokit/[email protected], action not found

Same here. Happens only on one repo among several others that use this GHA.

[notkurt]

Seeing this too. Once again, only on some of our repos, despite most of them using this action

##[debug]Evaluating job-level environment variables
##[debug]Evaluating job container
##[debug]Evaluating job service containers
##[debug]Evaluating job defaults
Prepare all required actions
Getting action download info
Error: Unable to resolve action octokit/[email protected], action not found
##[debug]GitHub.DistributedTask.WebApi.UnresolvableActionDownloadInfoException: Unable to resolve action octokit/[email protected], action not found
##[debug]   at GitHub.Services.WebApi.VssHttpClientBase.HandleResponseAsync(HttpResponseMessage response, CancellationToken cancellationToken)
##[debug]   at GitHub.Services.WebApi.VssHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)
##[debug]   at GitHub.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpRequestMessage message, Object userState, CancellationToken cancellationToken)
##[debug]   at GitHub.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpMethod method, IEnumerable`1 additionalHeaders, Guid locationId, Object routeValues, ApiResourceVersion version, HttpContent content, IEnumerable`1 queryParameters, Object userState, CancellationToken cancellationToken)
##[debug]   at GitHub.Runner.Worker.ActionManager.GetDownloadInfoAsync(IExecutionContext executionContext, List`1 actions)
##[debug]   at GitHub.Runner.Worker.ActionManager.GetDownloadInfoAsync(IExecutionContext executionContext, List`1 actions)
##[debug]   at GitHub.Runner.Worker.ActionManager.PrepareActionsRecursiveAsync(IExecutionContext executionContext, PrepareActionsState state, IEnumerable`1 actions, Int[32](https://github.com/Ten-Squared/XXXXXX/actions/runs/13233881014/job/36938851181#step:1:36) depth, Guid parentStepId)
##[debug]   at GitHub.Runner.Worker.ActionManager.PrepareActionsAsync(IExecutionContext executionContext, IEnumerable`1 steps, Guid rootStepId)
##[debug]   at GitHub.Runner.Worker.JobExtension.InitializeJob(IExecutionContext jobContext, AgentJobRequestMessage message)
##[debug]Finishing: Set up job```

[gowid-1000]

Same but on v2.1.0 🤔

[dariodevito]

Experiencing the same issue on octokit/[email protected]

[DavidSlayback]

Same on 2.1

[MatousJobanek]

We faced the same problem in one of our repos. To workaround the issue, we used SHA instead of the tag (you can also use main):

uses: octokit/request-action@dad4362715b7fb2ddedf9772c8670824af564f0d

[jpd4emis]

When forked to another org the repo works as expected with tags

[mpiltz]

We started experiencing this same issue couple of hours ago with v.2.3.1

[mpiltz]

We faced the same problem in one of our repos. To workaround the issue, we used SHA instead of the tag (you can also use main):

uses: octokit/request-action@dad4362715b7fb2ddedf9772c8670824af564f0d

I can confirm this also. Rolled the change to something like 20 repositories and everything seems to be working now. Earlier 4 out of the 20 repositories were failing even though the workflows are identical.

[pgodinhofortis]

Also affected by this, very strange

[mclavel]

Error: Unable to resolve action octokit/[email protected], action not found

😢

[canelmas]

can also confirm following fixes, strange tho

uses: octokit/request-action@main

[krshearman]

can also confirm following fixes, strange tho

uses: octokit/request-action@main

That's expected behavior @canelmas. You can use the branch, sha, or version number.

[pizzasaurusrex]

can also confirm following fixes, strange tho uses: octokit/request-action@main

That's expected behavior @canelmas. You can use the branch, sha, or version number.

@krshearman any idea why using the version number is currently unstable / not working?

[krshearman]

@pizzasaurusrex ~ no, I'm not sure why the version number is not working as expected. I'm digging around for answers at the moment.

[mortenbroesby]

It would be good to understand why this issue happened in the first place. A root cause analysis would be good for us to know that we can rely on this runner image in the future. Is this something a maintainer of this repository could action?

[gr2m]

Please use octokit/[email protected] as documented in the README. The repository is not setup correctly to work with git release tags.

[gr2m]

Sorry that's not true, it should work, e.g. for v2.4.0: https://github.com/octokit/request-action/tree/v2.4.0 (it does include the dist/ folder, not all actions I created do). Very odd. I don't have time to investigate myself right now, but hope someone else will be able to help. I'm curious to find out what is causing the problem