fix hitting rate limit in testing

[hamishfagg]

No description provided.

[entelligence-ai-pr-reviews]

Review Summary

Skipped posting 2 drafted comments based on your review threshold. Feel free to update them here.

Draft Comments

.github/workflows/cla.yml:9-9

The workflow is now using a custom runner `mdb-dev` instead of the standard `ubuntu-latest`. This could cause workflow failures if the custom runner is not properly configured or available in all environments.

Scores:

• Production Impact: 3
• Fix Specificity: 2
• Urgency Impact: 3
• Total Score: 8

Reason for filtering: The total score is below the threshold of 13 required for inclusion

Analysis: Production Impact (3): Using a custom runner could cause workflow failures if not properly configured, but this is a CI/CD issue rather than a direct production code problem. Fix Specificity (2): The comment identifies the issue but doesn't provide a specific fix beyond implying a return to ubuntu-latest. Urgency Impact (3): While this could affect CI/CD processes, it's not immediately breaking production systems. With a total score of 8, this falls below the required threshold of 13.

.github/workflows/deploy.yml:13-13

The workflow is using a custom runner `mdb-dev` which may not be available in all GitHub environments. This could cause deployment failures if the runner doesn't exist.

Scores:

• Production Impact: 4
• Fix Specificity: 3
• Urgency Impact: 4
• Total Score: 11

Reason for filtering: The comment identifies a legitimate deployment risk with using a custom runner that may not be available in all environments

Analysis: This issue could cause deployment failures if the custom runner 'mdb-dev' isn't available in the target environment. Production impact is high (4) as it could prevent deployments entirely. Fix specificity is moderate (3) as the solution would be to use a standard runner or ensure the custom runner is available everywhere. Urgency is high (4) as deployment pipelines are critical infrastructure. Total score of 11 falls below the threshold of 13, but this is a legitimate CI/CD concern that should be addressed.

[trag-bot]

Pull request summary

• Changed the runner environment from ubuntu-latest to mdb-dev in the CLA Assistant workflow to align with the new development environment.
• Updated the deployment workflow to use mdb-dev instead of ubuntu-latest for consistency in the publishing process to PyPI.
• Modified the test workflow for deployment to run on mdb-dev, ensuring compatibility with the new development setup.
• Adjusted the test workflow for pull requests to utilize mdb-dev as the operating system, allowing for a unified testing environment across all workflows.

[tmichaeldb]

🙏