Degradation due to 'token revocation' post script

[drehelis]

Token revocation has introduced a degradation to our workflows as we're using the token after the github action job is finished.
A switch whether a token should be deleted via post script or keep the old behaviour would be much appreciated.

[Petru-NicuDumitrache-TomTom]

We have a similar (not identical) problem:
Some of our workflows have steps that take a long time (>1hr). The token is created and used at the start of the step. Afterwards the step does some computations taking a very long time. In the "Post" step, the action tries to revoke the token, which in the meantime expired, leading to an error.
post_error.txt

[tibdex]

Can you make your long computations block the progress of the workflow so that the post script of this GitHub Action won't be triggered before they finish?

[Petru-NicuDumitrache-TomTom]

The Post does already trigger after the long computations.
It's just that by that time, the token is already gone from existence, so the action crashes trying to revoke it (I think).

[drehelis]

@Petru-NicuDumitrache-TomTom we've switched to getsentry/action-github-app-token@v2 which does basically the same. Just FYI...