Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use environment variables instead of output #1285

Closed
hf-krechan opened this issue Dec 19, 2024 · 1 comment
Closed

Use environment variables instead of output #1285

hf-krechan opened this issue Dec 19, 2024 · 1 comment
Labels
kind/enhancement New feature or request status/triage

Comments

@hf-krechan
Copy link

Description

The outputs are deprecated.

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

It would be nice if the outputs are also stored as environment variables like in this GH Action https://github.com/docker/metadata-action/tree/v5.6.1/?tab=readme-ov-file#outputs

@hf-krechan hf-krechan added kind/enhancement New feature or request status/triage labels Dec 19, 2024
@crazy-max
Copy link
Member

The outputs are deprecated.

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

outputs are not deprecated, it's just using set-output that has been deprecated in favor of GITHUB_OUTPUT env var, not the feature itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request status/triage
Projects
None yet
Development

No branches or pull requests

2 participants