Skip to content

fix(ci): use devbox-shellenv action to export env vars - #382

Merged
asalan316 merged 3 commits into
mainfrom
fix/devbox-shellenv-export
Oct 19, 2026
Merged

asalan316 merged 3 commits into
mainfrom
fix/devbox-shellenv-export

Conversation

@asalan316

@asalan316 asalan316 commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Problem

Release workflow failing at "Make devbox shellenv available" step. Manual printenv >> ${GITHUB_ENV} dumps all env vars including multi-line values (like Nix buildPhase), causing GITHUB_ENV parser error

Run eval "$(devbox shellenv)"
  eval "$(devbox shellenv)"
  printenv >> ${GITHUB_ENV}
  shell: /usr/bin/bash -e {0}
  env:
    NEW_TAG: v4.1.2
    latest_version: 0.18.4
    nix_version: 2.35.3
Error: Unable to process file command 'env' successfully.
Error: Invalid format '  echo " WARNING: the existence of this path is not guaranteed.";'

Failing GHA: https://github.com/cloudfoundry/app-autoscaler-cli-plugin/actions/runs/39232474453/job/118023879820

Solution

Use existing devbox-shellenv action that filters multi-line variables via env -0 parsing before exporting to GITHUB_ENV.

Testing

Screenshot 2026-10-19 at 14 33 19

Successful Build

@asalan316 asalan316 changed the title use devbox-shellenv action to export env vars\n fixes multi-line valu… fix(ci): use devbox-shellenv action to export env vars Oct 19, 2026
@asalan316
asalan316 merged commit 2c27800 into main Oct 19, 2026
2 checks passed
@asalan316
asalan316 deleted the fix/devbox-shellenv-export branch October 19, 2026 14:52
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.

2 participants