We had initially taken out the setup-node step in fear that it might interfere with the setup-node step of the calling action. This doesn't appear to be an issue after all.
Additionally, by including a setup-node step, the calling action doesn't have to worry about calling setup-node, which is a better solution for actions that otherwise wouldn't use node.
Finally, for actions already using node, we expose a node-version input so that the calling action can dictate which version of node symbol-upload uses.
CC'ing @nat-goodspeed, I don't think this will cause any issues in your pipeline, but just wanted to make you aware of this change 🙂. See #97 for more info.
We had initially taken out the setup-node step in fear that it might interfere with the setup-node step of the calling action. This doesn't appear to be an issue after all.
Additionally, by including a setup-node step, the calling action doesn't have to worry about calling setup-node, which is a better solution for actions that otherwise wouldn't use node.
Finally, for actions already using node, we expose a
node-version
input so that the calling action can dictate which version of node symbol-upload uses.Fixes #97