Potential Exposure of Sensitive Data in new "Set up runner" Step

[mariusfilipowski]

Description:
After migrating to the latest version, we've observed that there's a new step titled "Set up runner" in each job. This step logs all inputs of the workflow_dispatch event before any custom actions have a chance to mask values that should remain hidden.

This raises a couple of questions and potential concerns:

1. Is this step absolutely necessary for the workflow to function correctly?
2. If not, is there a way to disable or tweak it to prevent the exposure of sensitive data?

Code Reference:
The related code can be found here: start-runner.sh#L102

Request:

• Please clarify the necessity of the "Set up runner" step.
• Provide guidance on how we can disable or adjust this step to ensure sensitive information is properly masked.

Thank you for your assistance in resolving this issue.