mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #1467] act completely fails when encountering the newer GITHUB_STATE and GITHUB_OUTPUT file mechanism. #753
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#753
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JoshuaDodds on GitHub (Nov 26, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1467
Bug report info
Command used with act
Describe issue
When using the newer github environment files as described here:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
act completely fails and stops when encountering the new GITHUB_STATE and GITHUB_OUTPUT environment files. The older method with set-output still works but results in a warning in GH actions that:
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/I suspect the key to the fix to somewhat be in relation to this message from Github:
Action authors who are using the toolkit should update the @actions/core package to v1.10.0 or greater to get the updated saveState and setOutput functions.Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@vhoyer commented on GitHub (Nov 28, 2022):
Can confirm, is happening with me too
@ReenigneArcher commented on GitHub (Nov 28, 2022):
Same issue.
gives:
@djanowski commented on GitHub (Nov 30, 2022):
Works for me after installing latest master, e.g.
brew install act --HEAD.@vhoyer commented on GitHub (Nov 30, 2022):
so we need a release?
@ChristopherHX commented on GitHub (Nov 30, 2022):
I would suggest to fix your workflow to check for existence of env GITHUB_OUTPUT before writing to an unset env variable.
act v0.2.34 ( eta 2022 / 12 / 1 ) includes this feature, the older issues has already been closed.
Duplicate of #1386