chore: remove workflow command set-env #1627
No reviewers
Labels
No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
run-multi-platform-tests
No milestone
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
forgejo/runner!1627
Loading…
Reference in a new issue
No description provided.
Delete branch "aahlenst/runner:remove-set-env"
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?
The workflow command
set-envallows injecting additional variables into the environment. Unfortunately, it is difficult to use securely. Therefore, it is removed from Forgejo Runner. If workflows still useset-env, a warning will be printed. Contrary to GitHub Actions, it is not possible to restore it by setting the environment variableACTIONS_ALLOW_UNSECURE_COMMANDS=truebecause better alternatives exist. Workflows that need to amend the environment can write to$FORGEJO_ENV.Instead of:
Use:
See #1455.
ebc50cee0cb67fb912accascading-pr updated at actions/setup-forgejo#1043
Great, thanks!