stepman step-info -f json -i script
{"step_id":"script","step_version":"1.1.0","latest_version":"1.1.0","description":"Specify the script content and (optionally) the script runner\nbinary and this step will execute it.\n\nThe *runner* can even be a command, if it's available in the PATH\nand can execute the script it will work.\n\nFor example to run a [Go](https://golang.org/) Hello World \"script\"\nyou can define the content:\n\n package main\n import \"fmt\"\n func main() {\n fmt.Println(\"hello world\")\n }\n\nSet the *Execute with* parameter to `go run` and specify\na *script file path* because `go run` can only accept (at the moment)\nfiles with a .go extension (just specify `step.go` as the script path).\n\nIf the `go` binary can be found in the PATH your Hello World\nscript will run without any problem.","source":"https://github.com/bitrise-io/steps-script","steplib":"[email protected]:viktorbenei/bitrise-steplib.git","inputs":[{"key":"content","description":"Type your script here.\n\n**Make sure that it returns a non zero exit code in case of an error!**\nThe step will only fail if your script returns with a non zero exit code!\n","default_value":"#!/bin/bash\n\necho \"Hello Bitrise!\"","is_expand":false},{"key":"runner_bin","description":"The executor to be used for running the script.\nIf it's available in the PATH you can just\nspecify `ruby` or `python`, generally\nif you know the path of the executor you should\ndefine that, like `/bin/bash`.\n\nYou can even specify an execution command\nlike `go run` instead of just a binary.\n","default_value":"/bin/bash","is_expand":false},{"key":"is_debug","description":"If debug=yes the step will print debug infos about\nthe working dir, tmp file path, exit code, etc.\n","value_options":["no","yes"],"default_value":"no","is_expand":false},{"key":"working_dir","description":"This directory will be set as the current working\ndirectory for the script.\n","is_expand":true},{"key":"script_file_path","description":"Save the specified script content to this path\nbefore execution. The file will be removed after\nthe script finishes.\n\nGenerally you don't have to define this but\nthere might be cases where the file's name or path\nactually matters.\nFor example `go run` only accepts `.go` files.\n\nIf you specify a relative path then it will be\nrelative to the *working directory* (which you\ncan optinally specify as well).\n","is_expand":true}],"global_info":{}}
{"step_id":"script","step_version":"1.1.0","latest_version":"1.1.1","description":"Specify the script content and (optionally) the script runner\nbinary and this step will execute it.\n\nThe *runner* can even be a command, if it's available in the PATH\nand can execute the script it will work.\n\nFor example to run a [Go](https://golang.org/) Hello World \"script\"\nyou can define the content:\n\n package main\n import \"fmt\"\n func main() {\n fmt.Println(\"hello world\")\n }\n\nSet the *Execute with* parameter to `go run` and specify\na *script file path* because `go run` can only accept (at the moment)\nfiles with a .go extension (just specify `step.go` as the script path).\n\nIf the `go` binary can be found in the PATH your Hello World\nscript will run without any problem.","source":"https://github.com/bitrise-io/steps-script","steplib":"https://github.com/bitrise-io/bitrise-steplib.git","inputs":[{"key":"content","description":"Type your script here.\n\n**Make sure that it returns a non zero exit code in case of an error!**\nThe step will only fail if your script returns with a non zero exit code!\n","default_value":"#!/bin/bash\n\necho \"Hello Bitrise!\"","is_expand":false},{"key":"runner_bin","description":"The executor to be used for running the script.\nIf it's available in the PATH you can just\nspecify `ruby` or `python`, generally\nif you know the path of the executor you should\ndefine that, like `/bin/bash`.\n\nYou can even specify an execution command\nlike `go run` instead of just a binary.\n","default_value":"/bin/bash","is_expand":false},{"key":"is_debug","description":"If debug=yes the step will print debug infos about\nthe working dir, tmp file path, exit code, etc.\n","value_options":["no","yes"],"default_value":"no","is_expand":false},{"key":"working_dir","description":"This directory will be set as the current working\ndirectory for the script.\n","is_expand":true},{"key":"script_file_path","description":"Save the specified script content to this path\nbefore execution. The file will be removed after\nthe script finishes.\n\nGenerally you don't have to define this but\nthere might be cases where the file's name or path\nactually matters.\nFor example `go run` only accepts `.go` files.\n\nIf you specify a relative path then it will be\nrelative to the *working directory* (which you\ncan optinally specify as well).\n","is_expand":true}],"global_info":{}}
Note: I had two collection - and the output includes the script step / full JSON twice, I guess one for each collection