Self-hosted runners now reject malformed or blocklisted CLI arguments handed down by the server.
What's wrong with this entry?
Arguments the server hands to a self-hosted runner session are now checked against a name pattern and a blocklist before becoming CLI flags. Rejected ones are skipped and logged as "malformed" or "blocked", and the count of arguments actually applied is logged.
- Values starting with
-are passed as--name=valueso they are not parsed as a separate flag. - Log lines are assembled from a template beginning "[runner:session] Skipping ".
[runner:session] Skipping
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Self-hosted runners report when warm-up finished
Both mention self hosted runner
-
v2.1.236
Self-hosted runner releases a session only after its work finishes
Both mention self hosted runner
-
v2.1.236
Runner waits for sessions to be released before shutting down
Both mention self hosted runner