GitHub Actions · free-disk-space · Checked November 5, 2026

"Unable to resolve action. Repository not found: jlumbroso/free-disk-space": the action moved to lumbroso-commons on November 4, 2026

The free-disk-space action, which deletes preinstalled toolchains to make room on a hosted Ubuntu runner, moved from jlumbroso/free-disk-space to lumbroso-commons/free-disk-space on November 4, 2026. The GitHub website and API send the old name on to the new one, but GitHub Actions does not, so every job that still says uses: jlumbroso/free-disk-space fails in Set up job, before its first step, whichever version it names. Change the owner to lumbroso-commons: the tags and commit SHAs are the same as before.

What it looks like

From the report in the action's repository (free-disk-space #56, November 4, 2026):

Unable to resolve action. Repository not found: jlumbroso/free-disk-space

The whole job fails, not only the step. Actions resolves every uses: of a job in Set up job, before any if: is evaluated, so a free-disk-space step that would have been skipped stops the job too (truefoundry github-workflows-public #35).
Pinning does not help. The step in #56 named the full commit SHA of v2.0.0, and the fixes other projects merged that day changed @main and @v1.3.1 references alike (infino #1198). It is the owner that no longer resolves.

Why the old name stopped working

GitHub's documentation on renaming a repository says GitHub does not redirect calls to an action in a renamed repository, and that workflows using it fail with "repository not found". The same happened with this move to another owner. Everything else still follows it: https://github.com/jlumbroso/free-disk-space answers 301 with the new address, and so does the API, which is a quick way to find where an action went:

gh api repos/jlumbroso/free-disk-space --jq .full_name
# lumbroso-commons/free-disk-space

GitHub's documentation on transfers also says that when a repository that had more than 100 uses of GitHub Actions in the week before is transferred, its old owner and name are retired for good and cannot be used for a new repository. GitHub code search finds about 10,000 workflow files that still name jlumbroso/free-disk-space (November 5, 2026), against 18 for the new name.

The fix: change the owner

- uses: jlumbroso/free-disk-space@v1.3.1
+ uses: lumbroso-commons/free-disk-space@v1.3.1

It is the same repository, so each reference points at the same commit under the new owner (checked November 5, 2026):

v1.3.1: 54081f138730dfa15788a46383842cd2f914a1be (October 2023)
v1.3.2: 3f13feab2962a87273d379ebc36ea159527e6cc9 (September 17, 2026)
v2 and v2.0.0: ceedf095f4ec1a097402bc6bd80831f2e1a6fde6 (September 17, 2026)
main: 36e9a5af4eddb91fc11aec4c6f6f79b3cc0cb523, unchanged since September 17, 2026

To change every workflow in a repository at once (GNU sed, as on a Linux runner or in Git Bash):

grep -rl 'jlumbroso/free-disk-space' .github | xargs sed -i 's#jlumbroso/free-disk-space#lumbroso-commons/free-disk-space#g'

If the old name is in a reusable workflow or a composite action from another repository, the change has to be made there, and your job keeps failing until it is, or until you point it at a fixed commit of that repository. truefoundry/github-workflows-public fixed its build.yml and two other shared workflows this way (#35).
Dependabot does not make this change. Its pull requests from November 4 that bump the action to 2.0.0 keep the old owner, jlumbroso/free-disk-space@v2.0.0, so merging one leaves the job failing (intellij-runescript #59).
The action's README still shows uses: jlumbroso/free-disk-space@main (November 5, 2026), so a step copied from it has the old name.
If you move from v1 to v2 at the same time: swap is no longer removed unless you set swap-storage: true, and tool-cache is now preinstalled-runtimes (the old name still works, with a warning, until v3.0.0). The README's "Upgrading from v1 to v2" lists the changes.

On ubuntu-latest (Ubuntu 26.04): large-packages leaves Azure CLI and the browsers

With large-packages: true, the action removes package families one apt command at a time and turns a failed command into a warning. On the Ubuntu 26.04 image that ubuntu-latest is moving to, the last of those commands fails:

The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...

The 26.04 image installs PowerShell from its release tarball, because Microsoft's apt repository has no PowerShell for 26.04 yet (the image's install-powershell.sh). So there is no powershell package, and Ubuntu's archive has none either. apt resolves every name before it removes anything, so one name it cannot find means none of the six are removed (free-disk-space #41, about google-chrome-stable on 24.04 Arm runners; a comment of October 23 reports the same line on 26.04). Azure CLI, Chrome, Firefox and the Mesa drivers stay on the disk, and the warning is the only sign.

Until the action handles it, remove them in a step of your own after it. The image installs all four as packages:

- name: Remove what large-packages left on 26.04
  run: sudo apt-get remove -y azure-cli google-chrome-stable firefox libgl1-mesa-dri

PowerShell itself is in /opt/microsoft/powershell/7. #41 also has a script that asks dpkg which names are installed first, so the list keeps working when an image drops another package.

Forks of the action that do not turn the failure into a warning stop the job instead. Through descriptinc/free-disk-space, the Linux job of one project has failed this way since its first run on 26.04, on October 20 (llvm-aie #1461):

E: Unable to locate package powershell
##[error]Process completed with exit code 100.

Telling it apart

"Repository not found: jlumbroso/free-disk-space" in Set up job: the move on this page.
"unable to find version" with lumbroso-commons/free-disk-space: the owner is right and the tag or branch is not; the ones it has are listed above. Other reasons: "Unable to resolve action".
The step runs and prints "failed to complete successfully. Proceeding..." for the line with powershell: the 26.04 section above. On an Arm runner the same line fails on google-chrome-stable (#41).
The step passes and the job still runs out of disk later: no space left on a hosted runner has what each part frees and what else takes room on 26.04.

See failed jobs from IntelliJ IDEA

Pipeline Inbox for GitHub Actions Workflows, a plugin by Lesstep for JetBrains IDEs 2024.1 or later, lists the runs of all your repositories in an IDE tool window, with their jobs and steps, so a workflow that starts failing in Set up job stands out, and your current branch's runs are in the status bar. Reading is free; re-running failed jobs, cancelling, running workflows and reviewing deployments are Pro (US$1.50 a month, with a 30-day trial).

Get it on JetBrains Marketplace

GitHub and GitHub Actions are trademarks of GitHub, Inc.; Ubuntu is a trademark of Canonical Ltd.; Azure and PowerShell are trademarks of Microsoft Corporation; Google Chrome is a trademark of Google LLC; Firefox is a trademark of the Mozilla Foundation; IntelliJ IDEA is a trademark of JetBrains s.r.o. This page is not affiliated with, sponsored or endorsed by GitHub, Inc., Canonical, Microsoft, Google, Mozilla, JetBrains or the free-disk-space project.

More: "Unable to resolve action" · no space left on a hosted runner · "The ubuntu-latest label will migrate to Ubuntu 26" · GitHub Actions plugins for IntelliJ IDEA compared · 日本語