GitHub Actions removals · checked

set-output deprecated: is it disabled? Not as of 9 Oct 2026

set-output and save-state workflow commands: deprecated; no removal date, checked on 9 October 2026. Steps that print ::set-output or ::save-state still work and log a deprecation warning. GitHub postponed their removal on 24 July 2023 and has announced no new date. Since runner v2.332.0 (25 February 2026) it counts each job that uses them. The fix: Write echo "name=value" >> "$GITHUB_OUTPUT" (and >> "$GITHUB_STATE" for save-state); in an action's own code, use @actions/core 1.10.0 or later. Check your workflows now, with nothing to install: grep -rnE "::(set-output|save-state)" .github

$ grep -rnE "::(set-output|save-state)" .github

Run it from the repository root; it needs nothing installed and sends nothing anywhere. It finds each name as written in your workflow files; a value set in another file and passed in (a matrix from JSON, a reusable workflow's input) needs a look of its own. The fix is in the first paragraph above. The dates come from this data.

The facts

What
set-output and save-state workflow commands
Matches
Steps that print ::set-output, ::save-state, and an @actions/core dependency below 1.10.0
Effect
Warns; the job still runs
Announced
10 October 2022
Deprecated from
10 October 2022
Date
no datedeprecated; no removal date (checked 9 Oct 2026)
After the date
Steps that print ::set-output or ::save-state still work and log a deprecation warning. GitHub postponed their removal on 24 July 2023 and has announced no new date. Since runner v2.332.0 (25 February 2026) it counts each job that uses them.
The fix
Write echo "name=value" >> "$GITHUB_OUTPUT" (and >> "$GITHUB_STATE" for save-state); in an action's own code, use @actions/core 1.10.0 or later.

Notes

  • @actions/core before 1.10.0 writes set-output when an action calls core.setOutput, so an action's own dependency can be the source of the warning.

Sources

An email before each brownout, for the repos you watch, is not built.

It would re-read your workflows every day and email you a week and a day before each brownout or removal that would hit them, with no change to your repo. agentcheck's free hourly watch covers MCP servers only today. If you would pay for this one, say so with one click. The click is counted; nothing else is sent or stored.

Other GitHub Actions removals

Every removal, by date

actions-eol is a free tool from agentcheck, which runs scheduled checks of your endpoints and alerts you when an answer changes. Dates come from GitHub's own pages, read on the day shown; github.com only, since GitHub Enterprise Server keeps its own schedule.