Allow a list of environment variables to be passed publish workflows

[ConorMacBride]

"Any environment variables set in an env context defined at the workflow level in the caller workflow are not propagated to the called workflow." A new input for publish.yml and publish_pure_python.yml should be added which accepts a YAML list of environment variable names and values (encoded as a multiline string). Each of the build steps of both publishing workflows should call a Python script which parses the YAML input and writes each environment variable to the file defined by GITHUB_ENV.

[nabobalis]

Am I misunderstanding this:

If I define a env at the top of an actions file, it will not be passed to any publish step?

[ConorMacBride]

That's correct

[nabobalis]

That's correct

😭 All this time, I thought it was my CI script.

[nabobalis]

Thank you @ConorMacBride for working on this