Skip to content

Unable to process command '::set-env' #15

@sbernard31

Description

@sbernard31

I get those error using check-runs-action

Run dflydev/check-runs-action@v1.0.6
  with:
    token: ***
    checks: [
    { "id": "build", "name": "Build Code" },
    { "id": "unitTests", "name": "Unit Tests" }
  ]
  
    status: queued
  env:
    JAVA_HOME: /opt/hostedtoolcache/Java_Adopt_jdk/8.0.292-1/x64

Error: Unable to process command '::set-env name=DFLYDEV_CHECK_RUN_COLLECTIONS,::{"collections":[{"collection":"default","checkRuns":[{"status":"queued","id":"build","name":"Build Code","gitHubCheckRunId":6813436470},{"status":"queued","id":"unitTests","name":"Unit Tests","gitHubCheckRunId":6813436622}]}]}' successfully.

Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Since https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ maybe the code need to be adapted ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions