Skip to content

docs: [CI-23943]: Document hyphenated output variable behavior with act 0.2.89 - #11871

Open
imaditya55 wants to merge 1 commit into
mainfrom
docs/CI-23943-act-env-file-hyphenated-outputs
Open

imaditya55 wants to merge 1 commit into
mainfrom
docs/CI-23943-act-env-file-hyphenated-outputs

Conversation

@imaditya55

Copy link
Copy Markdown
Collaborator

…ct 0.2.89

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.

Description

Adds a note to the GitHub Action step docs (section: "Output variables from GitHub Actions steps") documenting a behavior change in the github-actions plugin images based on act v0.2.89 or later.
With act v0.2.89, the env-file parser (godotenv) rejects variable names containing characters outside [A-Za-z0-9_] and fails the entire step. The plugin now skips such names (e.g. hyphenated outputs like cache-hit and node-version from actions/setup-node) when writing act's env file. These outputs remain available as Harness output variables and can be referenced normally in later steps/stages.
This documents the change so support/customers have a reference if they notice hyphenated variables missing from the action's runtime environment after upgrading the plugin image.
Related plugin PR: drone-plugins/github-actions#32

Jira

https://harness.atlassian.net/browse/CI-24652

PR lifecycle

We aim to merge PRs within one week or less, but delays happen sometimes.

If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.

PRs must meet these requirements to be merged:

  • Successful preview build.
  • Code owner review.
  • No merge conflicts.
  • Release notes/new features docs: Feature/version released to at least one prod environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant