Skip to content

[ci] bump rayciversion, test_rules.txt updates default #59744

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
andrew-anyscale wants to merge 3 commits into from
Closed

[ci] bump rayciversion, test_rules.txt updates default #59744

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
720e22c
[ci] bump rayciversion, test_rules.txt updates default
andrew-anyscale Dec 29, 2025
7162905
Bump version from 0.22.0 to 0.23.0
andrew-anyscale Jan 7, 2026
9a25f6e
Merge branch 'master' into andrewpollack/bump-test-rules
andrew-anyscale Jan 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .rayciversion
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.21.0
0.23.0
12 changes: 12 additions & 0 deletions ci/pipeline/test_rules.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,8 @@
# file # File to match
# dir/*.py # Pattern to match, using fnmatch, matches dir/a.py dir/dir/b.py or dir/.py
# @ tag1 tag2 tag3 # Tags to emit for a rule. A rule without tags is a skipping rule.
# \fallthrough # Tags are always included, matching continues to next rule
# \default # Rule matches any file (catch-all)
#
# ; # Semicolon to separate rules

Expand All @@ -20,6 +22,10 @@
! linux_wheels macos_wheels docker doc python_dependencies tools
! release_tests spark_on_ray

\fallthrough
@ always lint
Comment on lines +25 to +26
Copy link
Collaborator

@aslonnie aslonnie Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reading this now, this feels a bit unnatural to read.

I feel that it should be something like:

*  # matching anything
@ always lint
\fallthrough # can only be right before a `;` line.
;

then this file is still going through a roughly speaking sequential logic flow

otherwise, maybe it is still more natural to write:

\always
@ always lint
;

Copy link
Contributor Author

@andrew-anyscale andrew-anyscale Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll make the change to update to the first proposal

Copy link
Contributor Author

@andrew-anyscale andrew-anyscale Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ray-project/rayci#355

;

python/ray/air/
@ ml train tune data linux_wheels
;
Expand Down Expand Up @@ -257,3 +263,9 @@ setup_hooks.sh
.fossa.yml
# pass
;

\default
@ ml tune train data serve
@ core_cpp cpp java python doc
@ linux_wheels macos_wheels dashboard tools release_tests
;