Skip to content

ci: add a stable required check so the test matrix can change - #100

Merged
vjohnson1-godaddy merged 1 commit into
mainfrom
ci/stable-required-check
Aug 31, 2026
Merged

vjohnson1-godaddy merged 1 commit into
mainfrom
ci/stable-required-check

Conversation

@vjohnson1-godaddy

Copy link
Copy Markdown
Contributor

Summary

  • Add a CI success job with a fixed name so branch protection is not pinned to one matrix cell (the macos + Python 3.9 check that blocked #99).
  • Drop the unused ::set-output step and the no-op matrix include.
  • Bump actions/checkout and actions/setup-python off Node 16-deprecated tags.

After this PR is green, point required checks at CI success (not Format and Tests (macos-latest, …)). Then rebase #99 and keep the ci-success job when resolving the ci.yml conflict.

Test plan

  • All Format and Tests matrix jobs pass
  • CI success is green
  • Settings → Branches → main: required check is CI success
  • Squash-merge this PR (merge commits are disabled on the repo)
  • Rebase fix: widen Python support to 3.11/3.12 (v3.0.1) #99 onto main and confirm it is no longer waiting on a dropped Python version

Made with Cursor

Branch protection was pinned to a single matrix cell (macos + a Python
version). Adding a CI success job with a fixed name keeps merges unblocked
when versions are added or dropped.

Co-authored-by: Cursor <cursoragent@cursor.com>
@vjohnson1-godaddy
vjohnson1-godaddy merged commit 23eb84f into main Aug 31, 2026
10 checks passed
@vjohnson1-godaddy
vjohnson1-godaddy deleted the ci/stable-required-check branch August 31, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants