Skip to content

Conversation

@ktdreyer
Copy link
Contributor

@ktdreyer ktdreyer commented Jul 3, 2025

Our main branch has many CI fixes and improvements that we want to incorporate into our stable release branch. This will increase our confidence in CI results for backport PRs.

Sync our .github directory on release-v0.10 with what is in the main branch (commit beae7f1).

These new tests also require the constraints-dev.txt file system. I've copied those changes from main as well, and regenerated constraints-dev.txt.

Our main branch has many CI fixes and improvements that we want to
incorporate into our stable release branch. This will increase our
confidence in CI results for backport PRs.

Sync our .github directory on release-v0.10 with what is in the main
branch (commit beae7f1).

These new tests also require the constraints-dev.txt file system. I've
copied those changes from "main" as well, and regenerated
constraints-dev.txt.

Signed-off-by: Ken Dreyer <[email protected]>
@ktdreyer ktdreyer force-pushed the backport-gh-actions-to-release-v0.10 branch from 8741277 to 555fa7b Compare July 3, 2025 16:10
@ktdreyer ktdreyer changed the title update .github from main (commit beae7f14) Draft: update .github from main (commit beae7f14) Jul 3, 2025
@ktdreyer
Copy link
Contributor Author

ktdreyer commented Jul 7, 2025

This uncovered two issues:

  1. In main, we still do not use launch-ec2-runner-with-fallback on all our tests that use AWS.
  2. This change pulls in the latest version of ruff, so that test fails now on new issues in the codebase. In the interest of keeping this branch stable and minimizing code changes, we could pin to the older version of ruff in this PR so that ruff will pass with existing code, and then we could cherry-pick the new ruff fixes separately.

@courtneypacheco
Copy link
Contributor

@ktdreyer - yes, let’s pin ruff for now to get it working.

@github-actions
Copy link

github-actions bot commented Oct 6, 2025

This pull request has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days.

@github-actions github-actions bot added the stale label Oct 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD Affects CI/CD configuration ci-failure release-branch stale testing Relates to testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants