Deprecated usages on Github Actions #1392

New Issue

OVERLORD · 2026-02-05T00:48:14+03:00

OVERLORD commented

2026-02-05 00:48:14 +03:00

Originally created by @dani-garcia on GitHub (Oct 20, 2022).

I've noticed some deprecation messages on our Github Actions, both here and in bw_web_builds, caused by two things:

The use of the save-state and set-output commands:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Some actions using Node 12 which is EOL:
https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

We have around six moths until they become errors, but I'm opening this issue to track them, as the build logs aren't very visible.

Originally created by @dani-garcia on GitHub (Oct 20, 2022). I've noticed some deprecation messages on our Github Actions, both here and in `bw_web_builds`, caused by two things: The use of the `save-state` and `set-output` commands: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ Some actions using Node 12 which is EOL: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ We have around six moths until they become errors, but I'm opening this issue to track them, as the build logs aren't very visible.

OVERLORD added the low priority label 2026-02-05 00:48:14 +03:00

OVERLORD closed this issue

2026-02-05 00:48:17 +03:00

OVERLORD commented

2026-02-05 00:48:21 +03:00

@BlackDex commented on GitHub (Oct 20, 2022):

They could be solved with some forked actions. But not sure if i like that.

@BlackDex commented on GitHub (Oct 20, 2022): They could be solved with some forked actions. But not sure if i like that.

OVERLORD commented

2026-02-05 00:48:23 +03:00

@dani-garcia commented on GitHub (Oct 20, 2022):

I assume the affected actions will be updated eventually, as I mentioned this isn't something we have to care about until April or so, but also I don't want it surprising us last minute. I'll mark it as low priority.

If by April there are still no updates, we can look into changing/forking to different actions, but we're using pretty popular actions so I don't think this will be an issue.

@dani-garcia commented on GitHub (Oct 20, 2022): I assume the affected actions will be updated eventually, as I mentioned this isn't something we have to care about until April or so, but also I don't want it surprising us last minute. I'll mark it as low priority. If by April there are still no updates, we can look into changing/forking to different actions, but we're using pretty popular actions so I don't think this will be an issue.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#1392