Repository navigation
chore(deps): update jlumbroso/free-disk-space action to v2 - #1587
Merged
Merged
Conversation
✅ Deploy Preview for devsydev canceled.
|
✅ Deploy Preview for images-devsy-sh canceled.
|
renovate
Bot
force-pushed
the
renovate/jlumbroso-free-disk-space-2.x
branch
4 times, most recently
from
October 19, 2026 14:54
f613d70 to
1ab2532
Compare
renovate
Bot
force-pushed
the
renovate/jlumbroso-free-disk-space-2.x
branch
from
October 19, 2026 15:08
1ab2532 to
9068442
Compare
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.3.2→v2.0.0Release Notes
jlumbroso/free-disk-space
v2.0.0: — three breaking changes, each with its reasonCompare Source
Breaking changes
swap-storagenow defaults tofalse. Closes #12 — reported and diagnosed by @zaikunzhang, whose proposed documentation fallback became the new FAQ. Removing swap can kill a job under memory pressure with no error pointing back at the cleanup step; a default should not break something that elementary.tool-cacheis renamedpreinstalled-runtimes. The old name still works until v3.0.0 and prints a deprecation warning. (Its default is unchanged:false, as it has been since 2022.) The new name says what actually breaks when you enable it: the runtimes thatactions/setup-node,setup-python,setup-go, andsetup-rubyrely on.dotnet: falseexempts .NET from every removal path, includinglarge-packages. Fixes #33 — reported by @ashleney; the overlap was first reported by @gmij in #6, and @ax3l explained the overlapping removal paths and a workaround. The policy is explicit, and this release applies it to .NET; future subject options add and test their own exemptions.Upgrading from v1 to v2
Most workflows need no change.
tool-cache:, rename it topreinstalled-runtimes:. The old name still works until v3.0.0 and prints a warning.swap-storage: true. It now defaults tofalse, because removing swap can kill a job under memory pressure with no error pointing back here (#12).dotnet: falseand were surprised that .NET was still removed, that is fixed — a specific option now overrides a general one (#33).Also in this release
A README FAQ ("what are the possible side-effects of these settings?"),
CONTRIBUTING.md, and a workflow example for running cleanup conditionally (#22). The reasons behind every design decision live indocs/adr/— including ADR-0007, the record of this release's default change, written the day it was decided.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.