prepare-next-development-version release step is broken

[drewhamilton]

See here. The most likely cause is that the ACCESS_TOKEN used to authenticate the Action is expired.

I don't have access to the repo's secrets (Settings/Environments) so I can't check on the existing token or update it. @donaldchickeme, can you confirm whether the existing ACCESS_TOKEN is expired?

[donaldchickeme]

Hey @drewhamilton, I have updated the PAT, could you try again? Sorry it took a while, I had to obtain permissions for this.

[drewhamilton]

It worked! The falling step passed and the bumped version was committed.