401 Error running API call through github-script

Start with the attached list-repo-status.yml workflow and debug log, then compare the last successful run with the first failing run. Check how github-script 6.3.3 receives and uses the organization secret, using the Postman result as a token-behavior comparison. Done means the workflow authenticates successfully and produces the repository list.

Edit: link to first failure
I am getting 401 “Bad Credentials” trying to run some api calls through github-script. This was working on Monday (Jan 9) but stopped working on Tuesday (Jan 10)

I have contacted GitHub Support and they have been able to reproduce the error. They say it is most likely due to the 3rd party action, "github-script" (6.3.3) causing this issue.
https://support.github.com/ticket/enterprise/15636/1960901

Steps to reproduce

1. Create PAT with Admin access (r/w) to repos and org/teams
   

2. Set an Org secret using the value from my PAT
   

3. Run the workflow manually (or from a push)
   

4. Failure with 401 error
   

Expected to produce a list of repositories
I have pared down the workflow to isolate the issue. Attached is the workflow (list-repo-status.yml) and the debug log
list-repo-status.yml
list-repo-status.debug.log.txt

Last successful run can be found:
https://github.com/teamkfinteg/reportscripts/actions/runs/3878744215

First failure (only difference was trying to replace trigger with cron
https://github.com/teamkfinteg/reportscripts/actions/runs/3885391826

I used Postman with the same token to test and it works as expected.

Desktop (please complete the following information):

• OS: Win10
• Browser: Firefox
• Version: 108.0.2 (64-bit)