Closed SensibleWood closed 7 months ago
Update on investigations.
The failure turned out to be deterministic, namely that it always failed when it hit the Postman Open Technologies organisation. This turned out to be because of the PAT: Postman has prohibited the use of classic tokens, so once a new token was generated and added to the secrets the build ran to completion.
Describe the bug
The build currently fails due to a new restriction at the Github API.
A 403 is returned where it should not be i.e. the permissions applied by Github should not result in a 403 being returned.
The behaviour was experienced in the past when there were too many active connections to the Github API. This has been tuned in the past down to 2 using the environment variables in the project.
To Reproduce
Steps to reproduce the behaviour:
Run either
yarn run build:data:metadata
oryarn run build:data:full
via the Github Actions workflow.Expected behaviour
The build should run to completion.
Additional context
This needs fixing to get the build up-and-running again, which will address #96 and #92 raised by @spacether as the JSON Schema Generator repository is correctly tagged using the
openapi31
topic.Actions: