Repository navigation
fix(ci): use devbox-shellenv action to export env vars - #382
Merged
Merged
Conversation
…es for github parser
This reverts commit d0e4542.
silvestre
approved these changes
Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Release workflow failing at "Make devbox shellenv available" step. Manual
printenv >> ${GITHUB_ENV}dumps all env vars including multi-line values (like NixbuildPhase), causing GITHUB_ENV parser errorFailing GHA: https://github.com/cloudfoundry/app-autoscaler-cli-plugin/actions/runs/39232474453/job/118023879820
Solution
Use existing
devbox-shellenvaction that filters multi-line variables viaenv -0parsing before exporting to GITHUB_ENV.Testing
Successful Build