CI is failing since #38. The failures have not been causing CI to fail on subsequent Speakeasy PRs because of the patch-speakeasy-pr.yml (which pushes a custom commit; GitHub actions identifies that the commit was pushed by the same event and chooses not to run CI again -- to prevent infinite loops).
The test failures seem specifically due to changes in the upstream OpenAPI Spec, and how our tests are generated. The fix (based on reading the Speakeasy docs) is to rebuild the tests?
We have a number of customizations to .speakeasy/test.arazzo.yaml though, and I'm unsure if speakeasy configure tests --rebuild will clobber those changes (seems like it will?).
CI is failing since #38. The failures have not been causing CI to fail on subsequent Speakeasy PRs because of the patch-speakeasy-pr.yml (which pushes a custom commit; GitHub actions identifies that the commit was pushed by the same event and chooses not to run CI again -- to prevent infinite loops).
The test failures seem specifically due to changes in the upstream OpenAPI Spec, and how our tests are generated. The fix (based on reading the Speakeasy docs) is to rebuild the tests?
We have a number of customizations to
.speakeasy/test.arazzo.yamlthough, and I'm unsure ifspeakeasy configure tests --rebuildwill clobber those changes (seems like it will?).