Automatically create OIDC token for pub.dev.

[isoos]

dart-lang/pub-dev#5769

[isoos]

/cc @jonasfj

[jonasfj]

Is there any reason to merge this before, we've tested it in production?

[isoos]

Is there any reason to merge this before, we've tested it in production?

I believe that after dart-lang/pub-dev#5975 gets to production, we can test this without merging by using the forked action in a workflow. There is no rush to merge it yet.

[isoos]

Note: I was able to test the latest version (augmented with the proper path for the dart executable) and it seems to me that a later dart pub publish -f would work as expected (using the PUB_TOKEN from the environment).

[mit-mit]

@isoos @devoncarew @jonasfj are we ready to move forward with this?

[jonasfj]

We could potentially do if [ -x $(which jq) ]; then echo '....'; fi so that we don't try anything if jq is missing and instead print a warning.
But it's probably present on most github runners, maybe if people do custom runners they'll run into missing jq / curl.

Otherwise, I see no risk in shipping this, I think we agree that this is what we want in the Github Action.

[isoos]

We could potentially do if [ -x $(which jq) ]; then echo '....'; fi so that we don't try anything if jq is missing and instead print a warning.

Updated script with jq existence check (using command -v).