Write the output to the $GITHUB_OUTPUT file

[john-jam]

This PR writes the output to the $GITHUB_OUTPUT file instead of echoing to stdout (see deprecation notes here).
Not 100% sure we have access to this file from within the container though.

[winterjung]

Thanks for your contribution! I didn't notice deprecations. Except env reference, lgtm!

[winterjung]

lgtm

[john-jam]

🚀 Do you plan on creating a new release soon?

[winterjung]

@john-jam Sure. I have been released split@v2.1.0.

[john-jam]

I am still hitting the warning but I guess it's because of the docker image (v2 tag) not yet updated.

[winterjung]

@john-jam I pushed docker image with v2 tag just before. I think you can use updated version of split actions now.

[RobKenis]

This is a breaking change lol

[winterjung]

@RobKenis Thanks for reporting. I didn't notice it's breaking changes. 🥲 Could you add more some details for me to resolve problem? (environment, usage of hosted runner, etc.)

[RobKenis]

These are the logs from the step

Run jungwinter/split@v2
  with:
    msg: my-project:./:./Dockerfile
    separator: :
    maxsplit: -1
  env:
    DOCKER_FILE_PATH: ./Dockerfile
    LEGACY_DOCKER_FILE_PATH: ./my-project/src/main/resources/docker/Dockerfile
    ARTIFACT_SRC_PATH: my-project-service-exec.jar
    ARTIFACT_DEST_PATH: my-project-service.jar
/usr/local/bin/docker run --name winterjungsplitv2_ed7206 --label 60e226 --workdir /github/workspace --rm -e "DOCKER_FILE_PATH" -e "LEGACY_DOCKER_FILE_PATH" -e "ARTIFACT_SRC_PATH" -e "ARTIFACT_DEST_PATH" -e "INPUT_MSG" -e "INPUT_SEPARATOR" -e "INPUT_MAXSPLIT" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKSPACE" -e "GITHUB_EVENT_PATH" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_ACTION" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true --network github_network_78054e55d29b48e3aed4a8e983a9d192 -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/runner/_work/_temp/_github_home":"/github/home" -v "/runner/_work/_temp/_github_workflow":"/github/workflow" -v "/runner/_work/_temp/_runner_file_commands":"/github/file_commands" -v "/runner/_work/my-project/my-project":"/github/workspace" winterjung/split:v2  "my-project:./:./Dockerfile" ":" "-1"
Error: $GITHUB_OUTPUT env is required.

We are using a hosted runner, running in an alpine-based container.
For now, we have pinned the version to v2.0.0, which resolves the issue for now.

[RobKenis]

Can you log a deprecation warning for v2 versions and make it breaking with v3 ?

[winterjung]

@RobKenis Agreed. I'll rollback the v2 docker image to 0f0d119 commit and prepare v3.