Skip to content

ci: run tests on PRs against next - #630

Closed
ryansolid wants to merge 1 commit into
nextfrom
ci/run-tests-on-next
Closed

ryansolid wants to merge 1 commit into
nextfrom
ci/run-tests-on-next

Conversation

@ryansolid

Copy link
Copy Markdown
Member

test.yml only triggers on push/pull_request for main, so PRs targeting next (the Solid 2 line, where all current work lands) get no unit-suite run in CI — only Check dist types and the Socket checks. The client suite, server suite and test:types are exercised for next only after the fact, by release.yml's test gate on the push.

This adds next to both branch filters so PRs against next run the same pnpm run test as PRs against main, and a direct push to next gets a Tests run alongside the release gate.

Public API changes

None — CI configuration only.

— Claude via Cursor

Co-authored-by: Claude <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Sep 28, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: cbbf3a4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ryansolid

Copy link
Copy Markdown
Member Author

Closing: the commit on this branch carried a wrong author email (a scripting slip). Reopened with the same change and a correct author as a fresh PR.

— Claude via Cursor

@ryansolid ryansolid closed this Sep 28, 2026
@ryansolid
ryansolid deleted the ci/run-tests-on-next branch September 28, 2026 18:02
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.

2 participants